Chunked encoding is always used in the back channel SLO call

Description

The SOAPClient in xmltooling uses chunkedEncoding by default. The SP code, in the prepareTransport call, sets the default to false, but the SLO has a different prepareTransport call that does not set this and is not configurable.

I'm finding that several servers do not deal well with chunked encodings...

Environment

None

Activity

Scott Cantor June 23, 2009 at 12:46 PM

Closing after releases.

André Cruz September 24, 2008 at 11:58 AM

Thanks. That was fast.

Scott Cantor September 24, 2008 at 11:56 AM

André Cruz September 24, 2008 at 11:50 AM

I'm having problems with Apache 1.3 + mod_perl.

It spits out a "chunked Transfer-Encoding forbidden". I searched the web and it seems to be a known limitation of apache 1.3. 2.0 and 2.2 work fine.

Scott Cantor September 24, 2008 at 11:28 AM

The SLO code uses the same SOAP layer as the rest of the code does. I think you mean the back-channel notification thing. That uses mostly default library settings, which would include that.

It's not a bug, either. I was led to understand that any standard server would handle chunked. It was assumed that only the weird ones that some SAML vendors were embedding would have problems with it, so I provided the option when doing SAML messaging.

What web server that the SP supports can't handle this?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Created September 24, 2008 at 11:15 AM
Updated June 23, 2009 at 12:46 PM
Resolved September 24, 2008 at 11:56 AM