There was a message sent to this list on June 29, reporting that
Apache::Test failed make test on an i386 OpenBSD 3.5 machine. I got
the same result on a G4 running OpenBSD 3.5. The error log is:
[quote]
# cat t/logs/error_log
[Fri Sep 24 12:56:40 2004] [notice] Initializing etag from
Seth Gordon wrote:
There was a message sent to this list on June 29, reporting that
Apache::Test failed make test on an i386 OpenBSD 3.5 machine. I got
the same result on a G4 running OpenBSD 3.5. The error log is:
[quote]
# cat t/logs/error_log
[Fri Sep 24 12:56:40 2004] [notice]
On Mon, 20 Sep 2004 14:44:57 -0400
Tod Thomas [EMAIL PROTECTED] wrote:
I have apache 2.0.51 compiled with mod_auth_ldap support. I was
wondering if anybody has tried flood to stress test this configuration
and could help me out.
I need to be able to randomly test a large number of users
Just a little correction: the code is being tested (under Windows and Linux)
from January 2004, not May.
Marc
- Original Message -
From: Marc Stern [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 23, 2004 1:41 PM
Subject: OCSP support added
I added support for
--On Thursday, September 23, 2004 12:43 PM +0100 Nick Kew [EMAIL PROTECTED]
wrote:
Basically it does the lookup/dispatch once per filter in the filterchain
per request. It checks that filter's providers until it finds a match.
So for anything you could do with an [Add|Set]OutputFilter[ByType]
Good evening All,
Thanks for the feedback... I just do a CVS build from time
to time to see if it compiles okay... no urgency as no customers!
:-)
Norm
- Original Message -
From:
Jean-Jacques
Clar
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Friday, September 24,
Justin Erenkrantz wrote:
--On Thursday, September 23, 2004 8:17 PM -0400 Bill Stoddard
[EMAIL PROTECTED] wrote:
Justin Erenkrantz wrote:
This little gem causes a regression. Because cache-handle is left
NULL,
we never cleanup stale entries in the cache (in cache_save_filter).
Once
[EMAIL PROTECTED] wrote:
Also, remove the broken conditional filter code as you can't reliably alter the
filter list once the response is started. (Regardless, cache_select_url()
has the freshness checks now.)
How does cache handle responses that are stale?
Are these objects revalidated
Graham Leggett wrote:
[EMAIL PROTECTED] wrote:
Also, remove the broken conditional filter code as you can't
reliably alter the
filter list once the response is started. (Regardless,
cache_select_url()
has the freshness checks now.)
How does cache handle responses that are stale?
Are
Hi,
Today, mod_setenvif does not provide a way to set environment
variable if something is interesting in response headers.
For example, in a reverse proxy architecture, this feature may allow to
gzip/deflate documents according to their Content-Type, and not only to
the request-uri
On 24 Sep 2004 16:15:31 +0200, Francois PESCE [EMAIL PROTECTED] wrote:
For example, in a reverse proxy architecture, this feature may allow to
gzip/deflate documents according to their Content-Type, and not only to
the request-uri or other client-side provided information that may hide
the
Bill Stoddard wrote:
Graham Leggett wrote:
[EMAIL PROTECTED] wrote:
Also, remove the broken conditional filter code as you can't
reliably alter the
filter list once the response is started. (Regardless,
cache_select_url()
has the freshness checks now.)
How does cache handle responses
On Sep 23, 2004, at 4:43 PM, William A. Rowe, Jr. wrote:
Please see http://httpd.apache.org/dev/dist/ for the current
httpd 2.0 release candidate. Among other items noted in
the CHANGES file, this candidate contains the patch for the
CAN-2004-0811 (cve.mitre.org) flaw in the processing of
Satisfy
Bill Stoddard wrote:
Are these objects revalidated (ie If-None-Match) or are the objects
discarded and fetched again from scratch?
Stale objects are discarded and fetched from the origin server.
Hmmm... that's quite a performance hit - suddenly what should be 304's
with no bodies are suddenly
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
What I've tried to do:
- Strip httpd.conf to only the config directives that almost everyone
needs to worry about.
- Put everything else in an extra/ directory, with commented-out Include
directives
Bill Stoddard wrote:
Stale objects are discarded and fetched from the origin server.
So we're missing all the code to handle RFC 2616 section 13.3. We're not
violating the RFC but our cache is sure not as efficient as possible.
What the CACHE_CONDITIONAL filter did was say if the cached response
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good. I think this is a good direction to move.
Any reason the Netware MPM part cannot be removed from near the top?
On Fri, 24 Sep 2004 13:12:30 -0400 (Est (heure d'été)), Joshua Slive
[EMAIL PROTECTED] wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
it looks good to me; I guess all those little pieces need
extra/foo-std.conf so that users will pick up
--On Friday, September 24, 2004 11:39 AM -0400 Bill Stoddard
[EMAIL PROTECTED] wrote:
So we're missing all the code to handle RFC 2616 section 13.3. We're not
violating the RFC but our cache is sure not as efficient as possible.
Put it this way: we were violating the RFC because our Expires
Graham Leggett wrote:
Bill Stoddard wrote:
Stale objects are discarded and fetched from the origin server.
So we're missing all the code to handle RFC 2616 section 13.3. We're
not violating the RFC but our cache is sure not as efficient as possible.
What the CACHE_CONDITIONAL filter did was say
Can an EOS bucket ever have data a filter needs to read?
--
Brian Akins
Lead Systems Engineer
CNN Internet Technologies
On Fri, 24 Sep 2004, Brian Akins wrote:
Can an EOS bucket ever have data a filter needs to read?
Nope. :)
That's what the APR_BUCKET_IS_METADATA flag (or whatever we ended up
calling it) is supposed to tell you.
--Cliff
As I recall the problem was that, at the time the CACHE_CONDITIONAL code
actually ran and tried to install the correct filter (in or out), it was
unable to alter the filter chain in a way that would allow the filter to run.
It was able to successfully add the filter, but it apparently was added
At 01:08 PM 9/24/2004, Paul Querna wrote:
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good. I think this is a good direction to move.
Any reason the Netware MPM part cannot
On Fri, 24 Sep 2004, William A. Rowe, Jr. wrote:
At 01:08 PM 9/24/2004, Paul Querna wrote:
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good. I think this is a good direction to
Cliff Woolley wrote:
On Fri, 24 Sep 2004, Brian Akins wrote:
Can an EOS bucket ever have data a filter needs to read?
Nope. :)
Thanks..
That's what the APR_BUCKET_IS_METADATA flag (or whatever we ended up
calling it) is supposed to tell you.
So read from any thing !APR_BUCKET_IS_METADATA
--
On Fri, 24 Sep 2004, Brian Akins wrote:
So read from any thing !APR_BUCKET_IS_METADATA
Yep. It doesn't hurt anything to read from a metadata bucket, you just
don't *have* to do it.
--Cliff
--On Friday, September 24, 2004 11:25 AM -0700 Justin Erenkrantz
[EMAIL PROTECTED] wrote:
caching-proxied-conditional requests. My preliminary thought is:
1) If cache_select_url() determines the cached response is out-of-date,
it can then add the 'If-None-Match' header (and any other headers as
At 02:27 PM 9/24/2004, you wrote:
On Fri, 24 Sep 2004, William A. Rowe, Jr. wrote:
At 01:08 PM 9/24/2004, Paul Querna wrote:
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good.
Maybe I am jumping in here out of turn, but let me ask the obvious
question. Why would we want to split the standard base httpd.conf file
up into multiple files? Doesn't this end up just confusing the average
user? One thing that I always tell new users of Apache is that rather
than trying
On Fri, 24 Sep 2004, Brad Nicholes wrote:
Maybe I am jumping in here out of turn, but let me ask the obvious
question. Why would we want to split the standard base httpd.conf file
up into multiple files? Doesn't this end up just confusing the average
user? One thing that I always tell new
31 matches
Mail list logo
