ECP soap message in logs?

Cantor, Scott cantor.2 at osu.edu
Wed Apr 29 15:05:09 EDT 2015


I don't speak Perl, but I spent several hours Monday determining that everything is working as it should on 2 containers, so unless somebody can produce a tcpdump trace showing the header set and that same error, I really can't justify spending more time on it right now. If the error is different then I'll review it.

I didn't see anything self evident in that script showing a content type header being set.

-- Scott



Sent with Good (www.good.com)


-----Original Message-----
From: Misagh Moayyed [mmoayyed at unicon.net<mailto:mmoayyed at unicon.net>]
Sent: Wednesday, April 29, 2015 02:53 PM Eastern Standard Time
To: 'Shib Users'
Subject: RE: ECP soap message in logs?


Thanks for the quick response.

I am actually using the latest ECP perl script provided by CILogon and
following up on that thread, I'd assumed the content-type was set and fixed
in that script by Scott K. it seems like it's setting the headers correctly,
if I am reading this right:
https://cilogon.org/ecp.pl

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, April 29, 2015 11:40 AM
To: Shib Users
Subject: Re: ECP soap message in logs?

On 4/29/15, 6:36 PM, "Misagh Moayyed" <mmoayyed at unicon.net> wrote:



>Is there a way to view the content of the ECP soap message in the IDP
>logs? I am troubleshooting an issue with ECP where the logs seem to
>indicate that the SOAP message received is invalid.  This is a
>SAXException with a “premature end of file” error.

Long thread on the dev list and bug discussion in Jira literally 2 days ago.
Your ECP client isn't setting content-type, and you can no longer get away
without that because of the use of Spring Web Flow in v3. Set content type
appropriately and it should work.

>I have adjusted the relevant log levels to DEBUG, but looking at the
>code, I can’t trace a statement that would log the received input stream.
>It seems to want to parse it directly.

It doesn't get logged until it's already been parsed.

-- Scott

--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150429/4677eb26/attachment-0001.html>


More information about the users mailing list