Shib IDP/ECP and input error

[Edwards, Wendy A]

FWIW, I ran it through the debugger, and the input stream that couldn¹t be
parsed was of type org.apache.catalina.connector.CoyoteInputStream , which
may be specific to Tomcat.

On 4/27/15, 12:28 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>On 4/27/15, 1:23 PM, "Scott Koranda" <skoranda at gmail.com> wrote:
>
>>The old version of that script did a POST to the IdP with the
>>Content-Type set incorrectly. The v2 IdP was forgiving but the v3 IdP
>>"needs" to see the proper Content-Type of "application/soap+xml".
>>
>>I expect this is actually a client error and not a v3 IdP error.
>
>That's a very weird error to get from that condition. I'm thinking this
>might be a Tomcat thing.
>
>>With my updated script I am able to make ECP work with v3 IdP with no
>>problems.
>
>That makes sense to me, but given the message I'm putting my money it's
>something Tomcat's doing that's consuming the stream ahead of the IdP for
>some reason. Apparently not in our code though if it's not showing up
>under Jetty.
>
>I don't know why it would affect only ECP though if that's the case.
>
>Hopefully you're right and it's just some really strange interaction if
>that content-type error happens.
>
>-- Scott
>
>-- 
>To unsubscribe from this list send an email to
>dev-unsubscribe at shibboleth.net