<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="HTML Tidy for Windows (vers 25 March 2009), see www.w3.org">
<meta name="Generator" content="MS Exchange Server version 14.03.0224.001">
<title>RE: ECP soap message in logs?</title>
</head>
<body>
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.<br>
<br>
I didn't see anything self evident in that script showing a content type header being set.<br>
<br>
-- Scott<br>
<br>
<br>
<br>
Sent with Good (www.good.com)<br>
<br>
<br>
-----Original Message-----<br>
<b>From: </b>Misagh Moayyed [<a href="mailto:mmoayyed@unicon.net">mmoayyed@unicon.net</a>]<br>
<b>Sent: </b>Wednesday, April 29, 2015 02:53 PM Eastern Standard Time<br>
<b>To: </b>'Shib Users'<br>
<b>Subject: </b>RE: ECP soap message in logs?<br>
<br>
<!-- Converted from text/plain format -->
<p><font size="2">Thanks for the quick response.<br>
<br>
I am actually using the latest ECP perl script provided by CILogon and<br>
following up on that thread, I'd assumed the content-type was set and fixed<br>
in that script by Scott K. it seems like it's setting the headers correctly,<br>
if I am reading this right:<br>
<a href="https://cilogon.org/ecp.pl">https://cilogon.org/ecp.pl</a><br>
<br>
-----Original Message-----<br>
From: users [<a href="mailto:users-bounces@shibboleth.net">mailto:users-bounces@shibboleth.net</a>] On Behalf Of Cantor, Scott<br>
Sent: Wednesday, April 29, 2015 11:40 AM<br>
To: Shib Users<br>
Subject: Re: ECP soap message in logs?<br>
<br>
On 4/29/15, 6:36 PM, "Misagh Moayyed" <mmoayyed@unicon.net> wrote:<br>
<br>
<br>
<br>
>Is there a way to view the content of the ECP soap message in the IDP<br>
>logs? I am troubleshooting an issue with ECP where the logs seem to<br>
>indicate that the SOAP message received is invalid. This is a<br>
>SAXException with a “premature end of file” error.<br>
<br>
Long thread on the dev list and bug discussion in Jira literally 2 days ago.<br>
Your ECP client isn't setting content-type, and you can no longer get away<br>
without that because of the use of Spring Web Flow in v3. Set content type<br>
appropriately and it should work.<br>
<br>
>I have adjusted the relevant log levels to DEBUG, but looking at the<br>
>code, I can’t trace a statement that would log the received input stream.<br>
>It seems to want to parse it directly.<br>
<br>
It doesn't get logged until it's already been parsed.<br>
<br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to<br>
users-unsubscribe@shibboleth.net<br>
--<br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net</font></p>
</body>
</html>