Hello,
Although I can see a lot of problems related to chunked encoding, it is
not clear to me if it is correctly supported in latests versions.
During tests with 2.2.4, I found the following problem: when the
back-end sends chunked encoding to an Apache reverse proxy (see below
for loaded modules), it seems that Apache does not understands it is
chunked encoded (although the header is present), and sends the complete
packet with the chunks length as part of the (non chunked encoded) message.
When suppressing the chunked encoding (by forcing HTTP 1.0 with "setenv
force-proxy-request-1.0"), it works smoothly.
Is this supposed to be one of the known bugs - I don't see corresponding
one (no mod_filter, mod_deflate, etc.)?
Details:
--------- Answer from the back-end ---------
HTTP/1.1 200 OK
Date: Tue, 01 Jun 2010 12:01:23 GMT
Server: ***back-end******
Content-Type: text/html; charset=utf-8
Content-Length: 28903
Transfer-Encoding: chunked
Connection: close
70d9
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
…
</body>
</html>
0
--------- Answer from the reverse proxy ---------
HTTP/1.1 200 OK
Date: Tue, 01 Jun 2010 12:01:23 GMT
Server: ***front-end******
Content-Type: text/html; charset=utf-8
Vary: Accept-Encoding,User-Agent
Content-Length: 28903
Connection: close
70d9
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
…
</body>
</html>
0
---------
Relevant loaded modules:
* mod_rewrite
* mod_substitute
* mod_include
* mod_proxy
* mod_proxy_http
Regards,
Nick
