On May 18, 2007, at 5:02 AM, Alex Sharaz wrote:

>
> 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?

I'm a little confused.  I can add a bug report to allow filtering of  
304 in the logs, but I'm not sure if there's another issue you're  
reporting.

-- Scott

>
> Alex
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:resin-interest- 
> [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



_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to