<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 32: timeout bug</title><link>https://sourceforge.net/p/ziproxy/bugs/32/</link><description>Recent changes to 32: timeout bug</description><atom:link href="https://sourceforge.net/p/ziproxy/bugs/32/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 13 Feb 2011 23:58:34 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ziproxy/bugs/32/feed.rss" rel="self" type="application/rss+xml"/><item><title>timeout bug</title><link>https://sourceforge.net/p/ziproxy/bugs/32/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When it comes to data which is fully loaded into memory for processing &lt;br /&gt;
(pictures being the most usual case) Ziproxy is (wrongly) considering timeout &lt;br /&gt;
the whole elapsed time, instead of inactivity timeout.&lt;/p&gt;
&lt;p&gt;The problem with this is when the picture takes too long to load (when link speed is terribly low, or when the picture is huge) it will timeout regardless the network activity.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Mealha Cabrita</dc:creator><pubDate>Sun, 13 Feb 2011 23:58:34 -0000</pubDate><guid>https://sourceforge.net1c6672f8a05b9567f5a42038d6a68e6e795a46cf</guid></item></channel></rss>