Re: HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Dan Poirier
Ruediger Pluem wrote: On 09/17/2008 10:00 PM, Dan Poirier wrote: I've looked at mod_expires doc and RFC 2616, but can't really tell what the right behavior is supposed to be in this case. Using mod_expire to set the expiration time to something like "access plus 1 hour", we see a browser reque

Re: HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Ruediger Pluem
On 09/17/2008 10:00 PM, Dan Poirier wrote: I've looked at mod_expires doc and RFC 2616, but can't really tell what the right behavior is supposed to be in this case. Using mod_expire to set the expiration time to something like "access plus 1 hour", we see a browser request a file, get back a

Re: HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Eric Covener
On Wed, Sep 17, 2008 at 5:16 PM, Manik Taneja <[EMAIL PROTECTED]> wrote: >> >> Is there any room in HTTP/1.1 for the client or server to save on the >> round-trips after the revalidation. Darn, misread some headers and 2.0.x and 2.2.x update the Expires on the 304 response. Sorry. -- Eric Cove

Re: HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Manik Taneja
On 18-Sep-08, at 2:21 AM, Eric Covener wrote: On Wed, Sep 17, 2008 at 4:46 PM, Manik Taneja <[EMAIL PROTECTED]> wrote: this behavior seems highly browser dependent. There may be a few possibilities as to why the browser doesn't send an IMS request. a. the browser cache is cleared b. the bro

Re: HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Eric Covener
On Wed, Sep 17, 2008 at 4:46 PM, Manik Taneja <[EMAIL PROTECTED]> wrote: > this behavior seems highly browser dependent. There may be a few > possibilities as to why the browser doesn't send an IMS request. > > a. the browser cache is cleared > b. the browser has a limited size cache and so this o

Re: HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Manik Taneja
this behavior seems highly browser dependent. There may be a few possibilities as to why the browser doesn't send an IMS request. a. the browser cache is cleared b. the browser has a limited size cache and so this object gets ejected due to lack of space. you could try increasing the size of

HTTP Protocol: How frequently should browser repeat requests after 304 responses?

2008-09-17 Thread Dan Poirier
I've looked at mod_expires doc and RFC 2616, but can't really tell what the right behavior is supposed to be in this case. Using mod_expire to set the expiration time to something like "access plus 1 hour", we see a browser request a file, get back a 200 with the expiration, and not request it aga