Shib IDP/ECP and input error
Cantor, Scott
cantor.2 at osu.edu
Mon Apr 27 16:55:49 EDT 2015
On 4/27/15, 4:51 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>On 4/27/15, 4:48 PM, "Edwards, Wendy A" <wedwards at illinois.edu> wrote:
>
>>If Tomcat is somehow eating the input stream, I¹d wondered if calling the
>>reset() method on the input at some point before the parser tried to read
>>it might fix the problem, hopefully without causing a problem with Jetty.
>
>It's nothing to do with Tomcat. I think it's Spring MVC, personally, but that's a total guess at this point. I think something there is deciding to consume the stream to decide something, and using a bogus content type avoids tripping that code.
It's more simple actually. Using *any* content type will make it work. That's sort of ok, or at least less bad, since technically SOAP requires text/xml and that works.
There is almost certainly a probe of some kind happening when no content type is sent, and that's consuming the stream.
I'll have to research how we can turn that off, but the good news is that using the strictly correct type will work in clients until it's fixed.
-- Scott
More information about the dev
mailing list