Shib IdP V3.2.1, Jetty 9.3.6, and HTTP/2
Tom Scavo
trscavo at gmail.com
Wed Feb 3 10:31:52 EST 2016
On Tue, Feb 2, 2016 at 9:40 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 2/2/16, 8:26 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
>
>>>We've googled and experimented and have come up short. Evidence is
>>>pointing to Jetty and its handling of HTTP/2 but we can't be sure.
>>
>>Since I know nothing about HTTP/2, I'll buy that.
>
> I assume you're basing it on something like this:
>
> http://sourceforge.net/p/curl/bugs/1482/
Yes.
> Looks like a curl issue, or missing feature anyway.
Well, that doesn't explain the browser behavior I'm seeing...only
Chrome on my Mac returns 404. Firefox and Safari have different
responses.
Basically, I think we want Jetty to stop trying to renegotiate the
SAML protocol. Apparently clients aren't ready for HTTP/2.
Tom
More information about the users
mailing list