[squid-users] redirecting body_pipe 0x85d6140*1 ( Slow PDF?? )

2009-04-23 Thread twinturbo
3.0.STABLE13


I am getting errors in my cachelog

client_side_request.cc(825) redirecting body_pipe 0x85d6140*1 from request
0x8520fd8 to 0x85206c8


Is this a problem, we do seem to be having problems opening PDF's in the
browser.

Rob





Re: [squid-users] redirecting body_pipe 0x85d6140*1 ( Slow PDF?? )

2009-04-23 Thread Amos Jeffries

twintu...@f2s.com wrote:

3.0.STABLE13


I am getting errors in my cachelog

client_side_request.cc(825) redirecting body_pipe 0x85d6140*1 from request
0x8520fd8 to 0x85206c8



This is Squid responding normally to receiving a 3xx: redirection reply 
from the web server.




Is this a problem, we do seem to be having problems opening PDF's in the
browser.


This is probably the known issue with Range: request headers issued by 
Adobe reader and the requests Squid is capable of processing.


Adobe Reader Web plugin has a problem with assuming that all external 
software can handle HTTP/1.1 overlapping Range: requests. But seems 
unable to handle the results when client is not. Such as Squid (and 
HTTP/1.0 servers) presenting the full object in response.


Some work is being done to make Squid more HTTP/1.1 compliant in that 
area to work better with Adobe.

 http://www.squid-cache.org/bugs/show_bug.cgi?id=2639
as a temporary measure the Accept-Ranges: none header might work when 
added to the replies.


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14
  Current Beta Squid 3.1.0.7