William A. Rowe, Jr. wrote:
(This posting maybe a dupe, I hope it's not)
Nope.
Okay, if this mail goes through, then the Apache.org listserver checks
whether a email address is subscribed not only using the From: header,
but using !MAIL FROM: and / or Return-Path:.
It's crufty and
On Tue, Feb 05, 2002 at 11:10:41PM -0500, Greg Ames wrote:
Has anyone tested this stuff on a system with Berkely DB? I would think that
would be a logical thing to do before yanking mod_auth_db.
FreeBSD's variant wasn't detected (I have to use BDB 4.0.14 for SVN,
so I never use anything
[EMAIL PROTECTED] wrote:
Tone down the logging levels for these two messages from
ERROR to NOTICE. It's something to note, but it isn't an
error worthy of logging by default.
I think you may have done the opposite of what you expected..
Aren't NOTICE messages *always* logged, regardless of
* On 2002-02-06 at 06:18,
Roy T. Fielding [EMAIL PROTECTED] excited the electrons to say:
I'm with Ryan (and we've had this discussion before). The code is
busted. Just fix it -- no need for a config change.
Works for me..
Let's see, then. Here are some test cases:
ServerName
From: Rodent of Unusual Size [mailto:[EMAIL PROTECTED]]
Does that seem about right?
Or in other words (just to make sure I understand), the ServerName directive
will no longer default to using port 80 if no port is specified. Instead,
it will default to using the actual port on which the
Jerry,
I've been trying to nail this one for a while now but have
not been able to recreate - do you have a testcase that will
generate the questionable POST request? What is catching the POST
on the server - a CGI? What platform is the server?
Please send any further info to me
Rodent of Unusual Size wrote:
Does that seem about right?
+1
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
A society that will trade a little liberty for a little order
On Wed, Feb 06, 2002 at 09:44:22AM -0500, Rodent of Unusual Size wrote:
Let's see, then. Here are some test cases:
[...]
Does that seem about right?
Yes, with the addition that any Port directive is used to create the
canonical name in preference to the port from the Listen directive, i.e.
Justin Erenkrantz wrote:
On Tue, Feb 05, 2002 at 11:10:41PM -0500, Greg Ames wrote:
Has anyone tested this stuff on a system with Berkely DB? I would think that
would be a logical thing to do before yanking mod_auth_db.
FreeBSD's variant wasn't detected (I have to use BDB 4.0.14 for
Tony Finch wrote:
Yes, with the addition that any Port directive is used to create the
canonical name in preference to the port from the Listen directive, i.e.
ServerName dotat.at
Port 8000
is the same as
ServerName dotat.at:8000
No, that just promulgates
On Wed, Feb 06, 2002 at 09:44:22AM -0500, Rodent of Unusual Size
wrote:
Let's see, then. Here are some test cases:
[...]
Does that seem about right?
Yes, with the addition that any Port directive is used to create the
canonical name in preference to the port from the Listen
ServerName MyServer.Com
Listen 1
Listen 2
Canonical name should be: MyServer.Com:port-used-by-the-request
I agree with all of them up through this last one. It's not that I
disagree with this, just that I'd be perfectly happy if the Canonical
name used 1 or 2 regardless
We're talking 2.0, so Port isn't available anyway.
Rodent of Unusual Size wrote:
Tony Finch wrote:
Yes, with the addition that any Port directive is used to create the
canonical name in preference to the port from the Listen directive, i.e.
ServerName dotat.at
On Wed, Feb 06, 2002 at 07:45:44AM -0800, Ryan Bloom wrote:
The Port directive was removed from 2.0, because it confuses too many
people.
Good :-)
Tony.
On Wed, Feb 06, 2002 at 09:44:22AM -0500, Rodent of Unusual Size wrote:
ServerName MyServer.Com
Listen 1
Listen 2
Canonical name should be: MyServer.Com:port-used-by-the-request
It's this case that makes me think we should just rename ServerName to
something like
On Wed, Feb 06, 2002 at 09:44:22AM -0500, Rodent of Unusual Size
wrote:
ServerName MyServer.Com
Listen 1
Listen 2
Canonical name should be: MyServer.Com:port-used-by-the-request
It's this case that makes me think we should just rename ServerName to
something like
On Wed, Feb 06, 2002 at 07:59:50AM -0800, Ryan Bloom wrote:
why don't you think that is possible with these changes? Right now, if
you don't specify a port in the ServerName directive, we use the default
port for the protocol. All we are saying, is if you don't specify a
port (i.e. you
Ryan Bloom wrote:
ServerName MyServer.Com
Listen 1
Listen 2
Canonical name should be: MyServer.Com:port-used-by-the-request
I agree with all of them up through this last one. It's not that I
disagree with this, just that I'd be perfectly happy if the Canonical
name used
ServerName MyServer.Com
Listen 1
Listen 2
Canonical name should be:
MyServer.Com:port-used-by-the-request
I agree with all of them up through this last one. It's not that I
disagree with this, just that I'd be perfectly happy if the
Canonical
name used 1 or
On Wed, Feb 06, 2002 at 11:15:36AM -0500, Rodent of Unusual Size wrote:
Ryan Bloom wrote:
ServerName MyServer.Com
Listen 1
Listen 2
Canonical name should be: MyServer.Com:port-used-by-the-request
I agree with all of them up through this last one. It's not that I
On Wed, Feb 06, 2002 at 07:04:12AM -0500, Rodent of Unusual Size wrote:
[EMAIL PROTECTED] wrote:
Tone down the logging levels for these two messages from
ERROR to NOTICE. It's something to note, but it isn't an
error worthy of logging by default.
I think you may have done the
On Wed, Feb 06, 2002 at 04:16:55PM -, [EMAIL PROTECTED] wrote:
trawick 02/02/06 08:16:55
Modified:server core.c
Log:
yet another tweak to empty brigade checking on entry to core_input_filter():
since APR_BRIGADE_EMPTY() assumes a non-empty brigade, we have to
On Wed, 6 Feb 2002, Justin Erenkrantz wrote:
You mean APR_BRIGADE_NORMALIZE assumes a non-empty brigade,
right? -- justin
Yeah... must have been a typo. Boy do I hate normalize... makes me need
another cup of coffee just thinking about it. :)
Normalize is definitely next on my hitlist.
Jeff Trawick wrote:
jean-frederic clere [EMAIL PROTECTED] writes:
Hi,
I have some problems with the httpd-2.0 (from CVS).
Whe compiled with Sun compiler it hangs at startup:
+++
$c
(some internal library calls omitted)
libsocket.so.1`getaddrinfo+0x524(ff31ac0c, 93c08,
jean-frederic clere [EMAIL PROTECTED] writes:
Back to reality, where we need to deal with this:
1) If you want to experiment with what might work around the
problem... You could replace APR_UNSPEC in ap_mpm_pod_check() with
AF_INET and see if that avoids the apparent WAIT_FOREVER
Justin Erenkrantz [EMAIL PROTECTED] writes:
On Wed, Feb 06, 2002 at 04:16:55PM -, [EMAIL PROTECTED] wrote:
trawick 02/02/06 08:16:55
...
An obvious variation of this fix would be to change APR_BRIGADE_NORMALIZE()
to deal with empty brigades.
You mean APR_BRIGADE_NORMALIZE
Greg Ames [EMAIL PROTECTED] writes:
my top priorities:
...
3. torture test the input side code with prematurely closed connections
I will claim to have done a fair amount of this (I haven't forgotten
the changes you requested). A series of tests with --with-efence
--enable-pool-debug was
Linux 2.2 2.4, HPUX
Broken on: Win32 [no error logging within service, other bugs]
for beta
-+1 : Aaron, Jim
++1 : Aaron
+0 : Lars, Justin, trawick
-0 : OtherBill
--1 :
I've now posted a patch against 2.0.31 that should fix all problems
seen so far that have been listed in STATUS.
It's at:
http://www.apache.org/~jerenkrantz/httpd-2.0.jre.patch
The changes are as follows:
* fix an AP_DEBUG_ASSERT() call.
- modules/http/http_protocol.c r1.391
* fix
Greg Ames wrote:
Justin Erenkrantz wrote:
I could have sworn that I committed that. Aha! In fact, I posted
a patch on 7 Jan for this.
applied, but:
configuring package in srclib/apr-util now
[...]
checking for ldap support...checking for gdbm.h... no
checking for db4/db.h... no
On Wed, Feb 06, 2002 at 10:43:28AM -0800, Aaron Bannert wrote:
I think it's obvious we're a no-go on .31 for beta -- let's remove this
section from STATUS and move toward .32
My preference is to incorporate a minimal patchset to .31 and call
that .32. (see my last post)
I have no faith in
If the list of available database formats is determined at
configure-/compile-time, it behooves us to only do binbuilds
on systems that have every single one for which we provide
support. It would more than just suck for a user to install
one of our binaries but be unable to use gdbm even though
On Tue, Feb 05, 2002 at 10:45:07PM -0500, Jeff Trawick wrote:
Adam Sussman [EMAIL PROTECTED] writes:
I'm seeing a lot of error messages like this in my error log under load with
lots of children (1300 or so):
...
#0 pthread_sighandler (signo=11, ctx=
{gs = 0, __gsh = 0, fs =
...so I cleaned up the orphans and restarted 2.0.29 at Wednesday, 06-Feb-2002
11:04:07 PST.
This was the same bug that Manoj noticed last week, where we don't handle ENFILE
on accept() properly:
[Wed Feb 06 06:46:53 2002] [error] (23)Too many open files in system:
apr_accept: (client socket)
On Wed, Feb 06, 2002 at 02:27:24PM -0500, Greg Ames wrote:
Ironically, I have a quick-n-dirty patch for that on the 2.0.31+ build I was
starting to test when I noticed this. But Jeff was able to break the new build
with premature closed connections, so I decided to go with .29. I think we're
Adam Sussman [EMAIL PROTECTED] writes:
make distclean
./configure --disable-threads old-parameters
make make install
That fixed the problem. So, is this the right solution? Should configure always
assume --disable-threads when it sees --with-mpm=prefork?
I don't believe
It has repeatedly been stated that only code changes can
be vetoed; releases cannot. Unfortunately, that doesn't
appear to be explicit in the project guidelines (see
URL:http://httpd.apache.org/dev/guidelines.html).
After looking at this a bit, what I think I'm finding is
that a showstopper
Justin Erenkrantz [EMAIL PROTECTED] writes:
I've now posted a patch against 2.0.31 that should fix all problems
seen so far that have been listed in STATUS.
...
If the group likes these fixes and deems it beta-worthy, we
can roll this as 2.0.32.
+1 (concept)
We need to resolve any
Justin Erenkrantz wrote:
I've now posted a patch against 2.0.31 that should fix all problems
seen so far that have been listed in STATUS.
It's at:
http://www.apache.org/~jerenkrantz/httpd-2.0.jre.patch
The changes are as follows:
* fix an AP_DEBUG_ASSERT() call.
-
I think you may have done the opposite of what you expected..
Aren't NOTICE messages *always* logged, regardless of LogLevel?
Oh, man. That sucks. It's #defined to be priority 5 in http_log.h,
but we ignore that level. Bah. That's bogus. NOTICE should be
priority 0 if we always
On Wed, Feb 06, 2002 at 02:54:26PM -0500, Greg Ames wrote:
I copied all the patches I have on my newest daedalus build to
http://www.apache.org/~gregames/ . The patches ending with .31.patch should
very closely resemble committed patches. Other than that, save_input.patch is
the usual
According to Ryan Bloom:
All we are saying, is if you don't specify a
port (i.e. you don't want to use a special port), use the same port that
the original request used.
+1
ciao...
--
Lars Eilebrecht - You might have mail.
[EMAIL PROTECTED]
Roy T. Fielding wrote:
syslog priorities are lame in general.
heh. take it to the next level; we could use something
with the flexibility of syslog.conf(5) and the broader
range of modern syslog facility codes.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
A showstopper, aside from a yet-to-be-reverted veto, can be moved from
one section of STATUS to another by the RM (or anyone, for that matter)
whenever they want. It is only a showstopper if we ALL agree it is.
The category only exists to simply remind us of what needs to be fixed.
Roy
On 6 Feb 2002 [EMAIL PROTECTED] wrote:
+FINAL RELEASE SHOWSTOPPERS:
+
+* [Ken] Test suite failures:
+ o worker is also failing some of the 'cgi' subtests
+ (see URL:http://Source-Zone.Org/Apache/regression/):
+Justin says: Worker should be fine and passes
...can be accessed on daedalus via
cd /usr/local/apache2_0_31.v3
gdb bin/httpd corefiles/httpd.core.1
This happened in test when Jeff was firing requests at it and prematurely
closing the connection. The backtrace looks like one that I should have a patch
for:
#0 0x8126b44 in ?? ()
#1
On Wed, Feb 06, 2002 at 03:16:09PM -0500, Greg Ames wrote:
...can be accessed on daedalus via
cd /usr/local/apache2_0_31.v3
gdb bin/httpd corefiles/httpd.core.1
This happened in test when Jeff was firing requests at it and prematurely
closing the connection. The backtrace looks like one
Roy T. Fielding wrote:
A showstopper, aside from a yet-to-be-reverted veto, can be
moved from one section of STATUS to another by the RM (or
anyone, for that matter) whenever they want. It is only
a showstopper if we ALL agree it is. The category only exists
to simply remind us of what
Cliff Woolley wrote:
On 6 Feb 2002 [EMAIL PROTECTED] wrote:
+FINAL RELEASE SHOWSTOPPERS:
+
+* [Ken] Test suite failures:
+ o worker is also failing some of the 'cgi' subtests
:
Sorry I never noticed this in the STATUS file before, but
this is exactly the
* On 2002-02-06 at 15:59,
William A. Rowe, Jr. [EMAIL PROTECTED] excited the electrons to say:
WRONG. You are proposing that one individual may block a release.
Yes.
That is diametrically opposed to the spirit of HTTP.
Rubbish. I mean, I disagree.
We are [now] treating showstoppers
Nobody can veto a release, period. It is therefore impossible for
anything to be a showstopper unless it is a pending veto of a commit
or the group makes a decision by majority of -1 on any release until
the problem is fixed. If the RM doesn't think that is the case,
then they should move the
On Wed, Feb 06, 2002 at 03:33:04PM -0500, Rodent of Unusual Size wrote:
Roy T. Fielding wrote:
A showstopper, aside from a yet-to-be-reverted veto, can be
moved from one section of STATUS to another by the RM (or
anyone, for that matter) whenever they want. It is only
a showstopper
From: William A. Rowe, Jr. [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 3:02 PM
From: Rodent of Unusual Size [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 2:53 PM
I think that's bogus, too. If someone thinks something is serious
enough to stop a release, they should be
* On 2002-02-06 at 16:15,
Roy T. Fielding [EMAIL PROTECTED] excited the electrons to say:
Nobody can veto a release, period. It is therefore impossible for
anything to be a showstopper unless it is a pending veto of a commit
or the group makes a decision by majority of -1 on any release
I add a showstopper to STATUS. One other person says -1, that's
not a showstopper. By my interpretation of the rules, they CANNOT
demote it from showstopper until there are enough people who would
vote to release (more +1s than -1s). This means that in order to
demote it, there would have to
* On 2002-02-06 at 16:38,
Roy T. Fielding [EMAIL PROTECTED] excited the electrons to say:
A showstopper is just an issue! Damnit guys, if you can't figure this out
I am going to remove the whole category from STATUS as being obviously bad
for your brain cells.
Then someone else will
There has never been a formal position on what a SHOWSTOPPER is. The
earliest uses were things that either should be fixed or we decide
aren't a problem anymore. That's my current understanding of it as
well. The RM has final authority... he can say I don't want to
release until we have these
Anyone have any details on:
* mod_autoindex displays the wrong icon for subdirectories on Unix
I'd like to see it fixed in 2.0.32, but I don't know the
details. -- justin
On Wed, 6 Feb 2002, Justin Erenkrantz wrote:
* mod_autoindex displays the wrong icon for subdirectories on Unix
I'd like to see it fixed in 2.0.32, but I don't know the
details. -- justin
I thought that was fixed?
--Cliff
--
* On 2002-02-06 at 16:48,
Jim Jagielski [EMAIL PROTECTED] excited the electrons to say:
People should go over the old STATUS files... they were back then
incredibly useful, but now they are bloated and confusing.
I've felt this way ever since shortly after they became
group-maintained
* On 2002-02-06 at 16:52,
Justin Erenkrantz [EMAIL PROTECTED] excited the electrons to say:
Anyone have any details on:
* mod_autoindex displays the wrong icon for subdirectories on Unix
I'd like to see it fixed in 2.0.32, but I don't know the
details. -- justin
I think Greg
On Wed, Feb 06, 2002 at 01:33:52PM -0800, Roy Fielding wrote:
I add a showstopper to STATUS. One other person says -1, that's
not a showstopper. By my interpretation of the rules, they CANNOT
demote it from showstopper until there are enough people who would
vote to release (more +1s than
Justin Erenkrantz wrote:
Anyone have any details on:
* mod_autoindex displays the wrong icon for subdirectories on Unix
I'd like to see it fixed in 2.0.32, but I don't know the
details.
It's fixed in HEAD last time I checked, with rev 1.93 of mod_autoindex. But
OtherBill said that
On Wed, Feb 06, 2002 at 08:18:26AM -0800, Aaron Bannert wrote:
Perhaps we should require the ServerName to have
a port when there are multiple Listen statements?
No, that disables the easy (and more useful and intuitive) way of
using the port that the request came in on.
Of course, you *can*
...as of Wednesday, 06-Feb-2002 16:35:14 PST. This is with patches for input
side seg faults, and for Berkeley DB support to allow authorized bugs.apache.org
access to work.
The httpd 2.0.29 parent died for the second time today shortly after noon
daedalus time, once again triggered by the
OtherBill, didn't you say that apxs works on Windows
for 1.2? Shouldn't the 'full' MSI install include it?
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
Millennium hand and shrimp!
From: Justin Erenkrantz [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 3:54 PM
Anyone have any details on:
* mod_autoindex displays the wrong icon for subdirectories on Unix
I'd like to see it fixed in 2.0.32, but I don't know the
details. -- justin
mod_dir is now a fixup.
From: Rodent of Unusual Size [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 8:43 PM
OtherBill, didn't you say that apxs works on Windows
for 1.2? Shouldn't the 'full' MSI install include it?
For 1.3.20 or so and on, yes it does work.
However, to install it, we would need to 'rewrite'
After talking with Ryan for a bit on IRC, he convinced me that the
pre_connection change is good and should be included in our next
release. If not, we'd release with a hook API we know is bogus.
I looked at the diffs between APACHE_2_0_31 and HEAD and I'm
fairly confident we're not going to
William A. Rowe, Jr. wrote:
From: Justin Erenkrantz [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 3:54 PM
Anyone have any details on:
* mod_autoindex displays the wrong icon for subdirectories on Unix
I'd like to see it fixed in 2.0.32, but I don't know the
details. --
I just added a Sleep(100) call right after the message that the 'child
process is running' message in ap_mpm_run. This resulted in 9 of 10
successful restarts when using the windows service manager. I was only
getting 2-3 prior to that. I know it's not a valid fix, but it seems
that Win
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2002/02/06 22:52:15 $]
Release:
2.0.32 : in development
2.0.31 : rolled Feburary 1, 2002.
2.0.30 : tagged January 8, 2002. not rolled.
2.0.29 : tagged November 27, 2001. not
one of the developer's over here stumbled on this error.
could this be similiar to the APR_initalize fixed earlier?
BTW.. this is 31 + justin's patches from his website I think.
this may be fixed in the most recent build of .31, but...
looks like ap_calculate_scoreboard_size() is 4 bytes off.
73 matches
Mail list logo
