Problems with Transfer-Encoding: chunked ?

I had some problems due to the fact that our Apache (1.3.26) server delivers content with Transfer-Encoding: chunked when the request specifies HTTP/1.1

• The output of the statistics script (used via geturl) contains length information before every (few) line of output
• When I try to Warning: Can't find topic "".""

(using Beta 3-Aug-2002)

-- NorbertGawor - 21 Nov 2002

Fixed my problems by changing HTTP/1.1 to HTTP/1.0 in

• lib/TWiki/Net.pm line 59
• bin/geturl line 38

until TWiki may become able to handle responses to HTTP/1.1 requests correctly.

-- NorbertGawor - 22 Nov 2002

Hi,

Interesting issue - chunked transfer encoding is a way for HTTP/1.1 servers to use persistent connections even though they don't know the length of the output before starting it. The trouble is that TWiki is saying it does HTTP/1.1 (required for some virtual hosts I think) but not accepting this encoding. Using LWP::Agent would probably fix this, of course...

Reverting to HTTP/1.1 seems to fix this, so perhaps it would be good to make the HTTP version a TWiki.cfg parameter, e.g. $httpVersion = "1.0". If you can do a patch for such a parameter, following the PatchGuidelines, including validation of the parameter in TWiki::initialize() (defaulting to 1.1), I'll see if we can include it.

-- RichardDonkin - 22 Nov 2002

This is a problem caused by ProxiedIncludesBrokenImplementationBug whereby TWiki claims to an origin server that it can cope with HTTP/1.1, when in fact it cannot. The patch attached to ProxiedIncludesBrokenImplementationBug - matching the PatchGuidelines - resolves this problem by permenently downgrading TWiki to stating it is only HTTP/1.0 compliant. (1.0 compliant systems can send 1.1 compliant requests - to a server the HTTP/ver part is telling the server what the client can handle not what style of request it's sending)

I'm marking this as a duplicate since there's a fix elsewhere.

-- MichaelSparks - 20 Jul 2003