Since people are talking about status code 304, I'm trying to sort out a 
problem herel.

I'm running a  wpad service for our univ network here using a Foundry 
ServerIron hardware load balancer ad 3 servers running 3.0.21

Wpad.dat.hull.ac.uk points to a virtual IP address on the load balancer which 
then funnels the request down to the 3 servers. Each (real) server has a number 
of virtual hosts on it one of which is wpad.hull.ac.uk. In addition to this 
I've got a default server that services any ip address requests to the real 
server. 

As I've discovered all sorts of applications  request wpad.dat and not just 
browsers. As far as the virtual host is concerned all requests come from the 
same IP address i.e. that of the ServerIron. Looking through the access.log 
file I see 

150.237.47.251 - - [18/May/2007:12:55:09 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:24 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:26 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:26 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:27 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:29 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:29 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "NSPlayer/11.0.5721.5145"
150.237.47.251 - - [18/May/2007:12:55:29 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "NSPlayer/11.0.5721.5145"
150.237.47.251 - - [18/May/2007:12:55:29 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "NSPlayer/11.0.5721.5145"
150.237.47.251 - - [18/May/2007:12:55:33 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:33 +0100] "GET /wpad.da HTTP/1.0" 200 247 
"-" "Mozilla/4.0 (compatible; MSIE 6.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:36 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:40 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:44 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "-"
150.237.47.251 - - [18/May/2007:12:55:45 +0100] "GET /wpad.da HTTP/1.0" 304 - 
"-" "Mozilla/4.0 (compatible; MSIE 6.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:48 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:51 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "-"
150.237.47.251 - - [18/May/2007:12:55:56 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:55:57 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:55:59 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:56:02 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:56:07 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:56:08 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:56:15 +0100] "GET /wpad.dat HTTP/1.1" 304 - 
"-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:56:23 +0100] "GET /wpad.dat HTTP/1.0" 200 
247 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Win32)"
150.237.47.251 - - [18/May/2007:12:56:23 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "Windows-Update-Agent"
150.237.47.251 - - [18/May/2007:12:56:25 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "-"
150.237.47.251 - - [18/May/2007:12:56:25 +0100] "GET /wpad.dat HTTP/1.1" 200 
247 "-" "-"


In most cases things like windows-Update-Agent requests the wpad.dat file and 
it is returned o.k. (200 247)  

Other times I get the 304 status code. We've got random occurrences where 
setting a browser to "auto detect proxy settings" doesn't work and i'm 
wondering if these occurrences could coincide with the 304 status codes I can 
see in the logs. I suppose the question is. Can i reconfigure something to get 
rid of the 304 entries in the logs?

Alex

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson
Sent: 17 May 2007 18:45
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] 304 status


On May 17, 2007, at 10:02 AM, Jean-Francois Lamy wrote:

> I am trying to understand how resin, apache and proxies interact with
> respect to caching.
>
> I have a jsp page which is meant to be always dynamic; headers are  
> used to
> prevent it from being cached.
> However, the page loads js, css, and various images, which I would  
> like to
> be cached.
>
> Currently,  the browser (IE7) requests those items, and Resin  
> returns 304
> (up-to-date) status.  The browser is NOT set to force request at  
> each page.
> This generates a lot of requests, which are painful when going through
> proxies.

What are the headers for the JSP page?

With no caching headers, Resin doesn't cache at all, i.e. no-cache is  
the default.  So the 304 is strange, unless the headers are telling  
Resin to cache.

(Serge's recommendations are good ones for general understanding of  
HTTP caching, but the described behavior seems odd.)

-- Scott

> Is there a recipe for forcing the JSP to always reload (my JSPs are  
> served
> through a dispatching servlet which does an include, and therefore  
> servlet
> is able manipulate the headers), and yet let the browser know that  
> the js
> and css it has in cache are just fine ?

> Jean-Fran├žois Lamy
> Technologies Teximus inc.
> www.teximus.com
> +1 514.878.1577 (Canada)
> +33(0) 8.70.44.49.02 (Europe)
>
>
>
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest



_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
*****************************************************************************************
To view the terms under which this email is distributed, please go to 
http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to