RE: [Rabbit-proxy-users] Re: Image Problems

[Samuel H. <Sam...@Co...>]

BTW.
With Mozilla I cannot get any errors at all.
Bugs seem to be just with Explorer.
I do not use Explorer (or dial-up) but many do.

Sam
 


-----Original Message-----
From: rab...@li...
[mailto:rab...@li...] On Behalf Of
Robert Olofsson
Sent: Monday, March 29, 2004 2:40 PM
To: Samuel Hill
Cc: rab...@li...
Subject: [Rabbit-proxy-users] Re: Image Problems


Samuel Hill wrote:

>I am using Rabbit Proxy with the following versions... ImageMagick 
>5.5.7 java version "1.4.2_04"
>Rabbit 2.0.29
>
>I am seeing problems when a browser has a cached image.
>For example, the browser will request the image from the proxy but it 
>does not show up in the browser (red x).
>  
>
Ok, that means that you are using IE, which version?
What happen if you enable http/1.1 and http/1.1 extensions? even for 
proxies?

When you get a red X, how does the image in rabbits cache look like?
(Get another client to access the admin pages and inspect the cache).

I know that there have been some problems with using a browser cache
with mixed compressed/uncompressed content. I do not see that however.
(but then I do not use rabbit much theese days, since my slowest net 
connection
is 2.5 Mb).

>I can see in the logs the request but cannot see anything in error 
>logs.
>  
>
What does the access log output? how many bytes were written?

If you can find a repetable test where this happens I would like to 
know. If
you also can snoop the network traffic I would be reallly glad (use 
ethereal or
the HTTPSnoopFilter in rabbit).

>If I clear the cache in the browser the image will show up. (The cached

>image is the compressed JPEG image)
>  
>
Seems like the client sends a conditional request or a range request and
rabbit returns something unexpected.

>Also, occasionally I will get "gateway timeouts" and I click refresh in

>the browser the page shows up. I do get an error in these cases...
>[29/Mar/2004:13:40:23 GMT][WARN][Error writing
>request:java.net.SocketTimeoutException: Read timed out]
>  
>
Any special site that this happens on?
Any repetable test case?

That could be a problem where rabbit believes that the connection is
persistent and sends a second request but the web server closes the 
connection.
(Note that writing the request succeds so rabbit is quite convinced that

the connection
is open. RabbIT ought to handle closes here so it is only a warning, its

allowed behaviour).

Sorry for not being able to help more, but give me more information and 
Ill see
what I can do.

/robo


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Rabbit-proxy-users mailing list Rab...@li...
https://lists.sourceforge.net/lists/listinfo/rabbit-proxy-users