Shib IDP/ECP and input error
Cantor, Scott
cantor.2 at osu.edu
Mon Apr 27 22:07:42 EDT 2015
On 4/28/15, 1:47 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>Wendy, I'm afraid you'll have to look into what you're doing, but our
>Tomcat-hosted IdP on shibboleth.net is working exactly like one in Jetty
>does. Any content type set, it works, no content type and it throws the
>error you're getting.
Refining this, it's actually not behaving unusually at all. It's not an
empty content-type that's buggy, but sending a totally incorrect
content-type of application/x-www-form-urlencoded.
What's happening is just a curl thing. Not setting a Content-Type header
on the command line results in a default of
application/x-www-form-urlencoded, and that fails as it should since
that's not true. If you set an empty Content-Type parameter, it doesn't
break it.
So this whole mess is really just a curl command line quirk.
-- Scott
More information about the dev
mailing list