Shib IDP/ECP and input error

[Edwards, Wendy A]

Thanks, Scott! I bet you're right -- there's something about the script I was using that caused problems, and the modifications were either incorrect or just didn't completely fix the issues. I'll try with the scripts that are known to work and look for a better fix for the testecp.sh script.


Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: "Cantor, Scott" <cantor.2 at osu.edu>
Date:04/27/2015 9:07 PM (GMT-06:00)
To: Shib Dev <dev at shibboleth.net>
Cc:
Subject: Re: Shib IDP/ECP and input error

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

--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150428/2ae8f690/attachment.html>