Shib IDP/ECP and input error

[Scott Koranda]

On Mon, Apr 27, 2015 at 4:55 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 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.

Ah. I didn't see that until now. The ECP profile version 2.0 says
explicitly soap 1.1, and so the content type is supposed to be
text/xml.

I will go back and update my example client (again) to use text/xml.

Thanks,

Scott K

>
> 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
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net