On Tue, Feb 03, 2004 at 09:51:39PM -, [EMAIL PROTECTED] wrote:
rederpj 2004/02/03 13:51:39
Modified:.Tag: APACHE_2_0_BRANCH CHANGES STATUS
modules/metadata Tag: APACHE_2_0_BRANCH mod_expires.c
Log:
*) Add support for IMT minor-type wildcards (e.g.,
* [EMAIL PROTECTED] wrote:
http://cvs.apache.org/viewcvs.cgi/httpd-2.0/modules/metadata/mod_expires.c?r1=1.45r2=1.46
Hrm. The whole check is probably segfaulting with something like
ExpiresByType text
isn't it? (Sorry for so late jumping in).
nd
Paul Querna wrote:
Forgot the new Patch procedure. Now added to bugzilla as PR 26650:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26650
FYI... posting to bugzilla is not absolutely required to have your patch
considered... it just ensures that it doesn't fall through the cracks
That introduced a warning to the 2.0 build:
mod_expires.c: In function `set_expiresbytype':
mod_expires.c:365: warning: passing arg 1 of `ap_strrchr' discards qualifiers from
pointer target type
the next version up in HEAD contains the fix
Geoffrey Young wrote:
That introduced a warning to the 2.0 build:
mod_expires.c: In function `set_expiresbytype':
mod_expires.c:365: warning: passing arg 1 of `ap_strrchr' discards qualifiers from
pointer target type
the next version up in HEAD contains the fix
[EMAIL PROTECTED] wrote:
rederpj 2004/02/04 06:37:40
Modified:.Tag: APACHE_2_0_BRANCH STATUS
Log:
(sheepishly) add a vote... (darn, missed the warning scrolling by. Good catch,
thanks).
we're up to 4 now... I'll commit the fix.
yes, I was just about to post this :)
:)
(thank goodness for cron)
and -Werror :)
so I guess that makes at least two who build nightly. just out of
curiosity, is anyone else?
--Geoff
Geoffrey Young wrote:
(thank goodness for cron)
and -Werror :)
vendor compilers for Unix-ish systems have a nasty habit of rejecting invalid
C... no non-default settings required ;)
Jeff Trawick wrote:
The buglet was that prctl() was issued always when available, when goal
(to be consistent with httpd 2.x) was to only issue it if admin has
coded CoreDumpDirectory.
+1 - reviewed and tested.
Greg
Hi list,
attached patch fixes the bug# 26152 as described in
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26152
Main purpose was to handle backslashes in the URI to avoid misleading
interpretation via the underlying cygwin OS layer, which allows
backslashes as directory delimiters.
Hi list,
in order to have dbm support for mod_rewrite and correct the build and
install process on the cygwin platform, please see attached patch.
Stipe
mailto:[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470
On Wed, Feb 04, 2004 at 05:48:48PM +0100, Stipe Tolj wrote:
Hi list,
attached patch fixes the bug# 26152 as described in
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26152
Main purpose was to handle backslashes in the URI to avoid misleading
interpretation via the underlying cygwin
Anyone already working on switching to it?
I'm starting now with the code. Please speak up, if there's already work done.
nd
On Sun, Feb 01, 2004 at 01:30:56AM +, Pier Fumagalli wrote:
I found a small bug in mod_disk_cache...
CacheMinFileSize and CacheMaxFileSize process the argument with atoi(),
which simply means that they'll get -1 if the value is quite large (I
need to cache some big files)...
At the
Hi,
I was playing with ssldump for the data transferred b/w browser and Apache
(2.0.48) - and realized that the Apache2 (+ mod_ssl) does not send the Alert message
to the client before closing the connection.
-Madhu
Here's the error_log output from Apache 1.3 (+ mod_ssl)
[04/Feb/2004
I had some offline feedback for my previous Location speeder-upper which I
though had merit. That patch skips the directory walk when it detects a
SetHandler directive inside of a Location block. The jist of the criticism was
that some user might have a Location block with a URI that overlaps
* [EMAIL PROTECTED] wrote:
If there are sites out there that ignore the piece about the content living
outside the filesystem, my previous patch which requires no new
configuration might create problems. This version adds an OutsideFilesystem
directive, only valid in Location, to eliminate
On Wed, 4 Feb 2004, [ISO-8859-15] André Malo wrote:
* [EMAIL PROTECTED] wrote:
If there are sites out there that ignore the piece about the content living
outside the filesystem, my previous patch which requires no new
configuration might create problems. This version adds an
* Joshua Slive [EMAIL PROTECTED] wrote:
On Wed, 4 Feb 2004, [ISO-8859-15] André Malo wrote:
* [EMAIL PROTECTED] wrote:
If there are sites out there that ignore the piece about the content
living outside the filesystem, my previous patch which requires no new
configuration might
At 03:39 PM 2/4/2004, [EMAIL PROTECTED] wrote:
But then if I play devil's advocate, someone could see the new directive and turn it
on when it's not appropriate and cause Bad Things to happen. Mainly I'm looking for
comments on whether this should be configurable or not.
Yes, I'm one who will
Quick handlers are not for filtering content. Quick handlers assume
all responsibility for the request, e.g. proxy content servers. In fact this
particular hook was debated for quite a while (with some believing it was
inherently a bad thing.)
I don't believe that redirects have the opportunity
-1. Reject the request with a 400 error instead.
Roy
I am curious about what it would take to use an alternate protocol at
layer 4 with apache.
I have already posted to the users list and was referred here.
Apache can communicate with several TCP protocols but I have a module
project which needs UDP communications as well. I have searched the
At 05:45 PM 2/4/2004, Roy T. Fielding wrote:
-1. Reject the request with a 400 error instead.
++1 to Roy's suggestion.
I believe that Win32 may accept the back slash (with the changes proposed
for the cygwin port.) However ... here's the trick ... the cygwin httpd port
is emulating Unix, so it
On February 4, 2004 04:39 pm, Mathihalli, Madhusudan wrote:
Hi,
I was playing with ssldump for the data transferred b/w browser and
Apache (2.0.48) - and realized that the Apache2 (+ mod_ssl) does not
send the Alert message to the client before closing the connection.
Funnily enough, I
Hi Roy,
Roy T. Fielding wrote
-1. Reject the request with a 400 error instead.
actually a standard (apache layout) install (from source) on a linux
box with the URI described in the bug report gives also a 404, and
*not* a 400 in response.
So we get the same behaviour on cygwin as on
William A. Rowe, Jr. wrote:
At 05:45 PM 2/4/2004, Roy T. Fielding wrote:
-1. Reject the request with a 400 error instead.
++1 to Roy's suggestion.
I believe that Win32 may accept the back slash (with the changes proposed
for the cygwin port.) However ... here's the trick ... the
Stipe Tolj wrote:
Hi Roy,
Roy T. Fielding wrote
-1. Reject the request with a 400 error instead.
actually a standard (apache layout) install (from source) on a linux
box with the URI described in the bug report gives also a 404, and
*not* a 400 in response.
So we get the same
-Original Message-
From: Geoff Thorpe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 04, 2004 5:56 PM
To: [EMAIL PROTECTED]
Cc: Mathihalli, Madhusudan
Subject: Re: mod_ssl not sending Alert upon close ?
On February 4, 2004 04:39 pm, Mathihalli, Madhusudan wrote:
Hi,
I was
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2004/01/28 21:22:20 $]
Release:
1.3.30-dev: In development
1.3.29: Tagged October 24, 2003. Announced Oct 29, 2003.
1.3.28: Tagged July 16, 2003. Announced ??
1.3.27: Tagged
APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2004/01/04 15:08:00 $]
Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
2.1.0 : in development
Please consult the following STATUS files for information
on related
I'm totally confused now :) Do you want Apache to handle the UDP request
as an HTTP request? Or do you want a UDP port that does something else?
First if you want a pool of UDP listeners, explore the MPM - it's the MPM's
job to dispatch requests from TCP, so it would make sense to build upon
32 matches
Mail list logo
