Hi,

we have a setup where pound is the load balancer in front of a NGinx Long Polling server. I can reproduce an issue where after a long poll ends with "HTTP 304 not modified", the next HTTP response message is corrupt. You'll get in Google Chrome messages like this:

0

HTTP/1.1 200 OK

Server: nginx/1.0.14

Date: Tue, 08 May 2012 05:58:03 GMT

Content-Type: application/json

Last-Modified: Tue, 08 May 2012 05:57:33 GMT

Connection: close

Etag: 0

Transfer-Encoding: chunked

2159

{"REMOVED_BODY_CONTENT"}

I also have this issue with a Lighttpd behind Pound using chunked encoding.

Google Chrome is really strict in it's parsing rules for chunked encoding. See http://code.google.com/p/chromium/issues/detail?id=39206#c12

I have found the issue with pound 2.5 but have also the same error with pound 2.6 and 2.7.

When I use Apache as proxy everything works fine.

--
Dennis Becker becker@sipgate.de
Telefon: +49 (0) 211-63 55 55-97
Telefax: +49 (0) 211-63 55 55-22

sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391

www.sipgate.de - www.sipgate.at - www.sipgate.co.uk