<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 33: Keep-Alive interpretation</title><link>https://sourceforge.net/p/ziproxy/bugs/33/</link><description>Recent changes to 33: Keep-Alive interpretation</description><atom:link href="https://sourceforge.net/p/ziproxy/bugs/33/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 28 Feb 2011 12:28:56 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ziproxy/bugs/33/feed.rss" rel="self" type="application/rss+xml"/><item><title>Keep-Alive interpretation</title><link>https://sourceforge.net/p/ziproxy/bugs/33/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ziproxy 3.2.0 does not send the response to a request (http://cp32585.edgefcs.net/crossdomain.xml) on to the client. although it received it. The attachment contains a full capture of the tcp connections between client/proxy and proxy/server.&lt;/p&gt;
&lt;p&gt;The server's response contains content-length field and a keep-alive. Ziproxy first sends a 200-response to the client, but not the response body (or not fully, the gziped data is incomplete). After 90 seconds it sends another response to the client (408 Request Timeout).&lt;/p&gt;
&lt;p&gt;As far is I see, ziproxy should recognize the end of the whole response by the content-length header and close the connection to the server, regardless of the keep-alive header from the server.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 28 Feb 2011 12:28:56 -0000</pubDate><guid>https://sourceforge.net5cf5f1cfa13de6ffbad229beb14447fa1160b15f</guid></item></channel></rss>