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
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
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
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
On Wed, Sep 17, 2008 at 12:45 PM, Eric Covener <[EMAIL PROTECTED]> wrote:
> I believe this is now correct w/ r696366 if you want to doublecheck.
Jim, I think you re-broke it with your last two CHANGES updates. You
left it with two "PR 45445" and no "initial-not-pooled" (and latter
is committed)
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
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
Hi,
I have a ubuntu server with a linux 2.6.24 kernel running on an HP
proliant server with 64-bit 2 x dual-core, 4 GB ram. I'm trying to
measure the peak request rate with the apache server configured as
forward proxy and so I load this system with 5000 req/sec from a
polygraph setup
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
On Wed, Sep 17, 2008 at 12:41 PM, Eric Covener <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 17, 2008 at 10:23 AM, <[EMAIL PROTECTED]> wrote:
>> Author: jim
>> Date: Wed Sep 17 07:23:35 2008
>> New Revision: 696316
>>
>> URL: http://svn.apache.org/viewvc?rev=696316&view=rev
>> Log:
>> * mod_proxy: Add
On Wed, Sep 17, 2008 at 10:23 AM, <[EMAIL PROTECTED]> wrote:
> Author: jim
> Date: Wed Sep 17 07:23:35 2008
> New Revision: 696316
>
> URL: http://svn.apache.org/viewvc?rev=696316&view=rev
> Log:
> * mod_proxy: Add the possibility to set a separate connection timeout for
>backend workers.
>
On Sep 16, 2008, at 3:58 PM, Ruediger Pluem wrote:
On 09/16/2008 09:05 PM, Justin Erenkrantz wrote:
On Sun, Sep 14, 2008 at 7:02 AM, Ruediger Pluem <[EMAIL PROTECTED]>
wrote:
Given the fact that Jim plans to T&R 2.2.10 mid-, late September
I triaged through the STATUS file. There are 10 pr
I need to add background pinging of proxy backends to Apache 2.2. [I'll
contribute code back, but may or may not be able to get it into a form
that is acceptable for inclusion in Apache.]
Unfortunately, it is clear to me I do not have nearly the familiarity
with the Apache APIs to make this p
13 matches
Mail list logo
