Jancs wrote:
Quoting Amos Jeffries <squid3@xxxxxxxxxxxxx>:
Janis wrote:
I succeded in setting up chain of proxies using ssl for
inter-communication, but - i lost possibility to tunnel https
requests - instead of it i get empty page without any messages.
Where should I look to correct this?
Could be TCP issues with window scalin, or ECN, or HTTP server issues
with chunked-encoding. Google has the answers to both.
in the cache.log I am getting such messages:
192.168.0.1 TCP_MISS/000 0 CONNECT sourceforge.net:443 -
FIRST_UP_PARENT/__ip__ -
(Squid 3.0.ST5)
Thats the access.log file not the cache.log file. Still. This brings to
mind a bug just fixed in the last few days.
What does cache.log have to say about those failed requests?
What version is the parent cache? Same details from them if possible.
And finally, does the patch for the bug change things?
http://www.squid-cache.org/bugs/show_bug.cgi?id=2332
Amos
--
Please use Squid 2.6.STABLE20 or 3.0.STABLE5
