/Shibboleth.sso/SAML2/POST 500 Chrome
cantor.2 at osu.edu
Mon Sep 15 13:07:39 EDT 2014
On 9/15/14, 1:02 PM, "Teresa Fasano" <t.fasano at cineca.it> wrote:
>At the Apache logs I see:"XML error(s) during parsing, check log for
And the same or more detail will be in native.log
Either way, you can't fix it from the server end alone. If the browser
won't send the data cleanly, it isn't going to work. You will have to get
networking people involved, perform traces on the server end of the
connection to see what's happening (probably with ssldump), that sort of
thing. And have networking people willing to believe you. You also have to
account for the possibility that the data is corrupted before it hits your
network, assuming that the whole exchange isn't local.
Alternatively, you can switch to artifact binding, and hope that the
problem doesn't affect any application use of POST.
More information about the users