httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Stuff to do:
* finish the t/TEST exit code issue (ORed with 0x2C if
framework failed)
* change existing tests that frob the
On Wed, Dec 07, 2005 at 01:18:32AM -0600, William A. Rowe, Jr. wrote:
Do mirrors even validate any server signature for rsync? If not this
argument is blowing smoke. For that matter, we could even endorse the
use of ssl privately to our mirrors on the backend, with server cert
validation to
-On December 7, 2005 2:00:19 AM +0100 Ruediger Pluem [EMAIL PROTECTED]
wrote:
The patches to mod_proxy_http we identified here on list do indeed work
and are in as r354628.
Sorry for stepping in that late into the discussion, but wouldn't it be
better to fix that after the return from
So no-one is interested in testing?
How is Apache 64bit on other systems? Did it give a preformance boost?
~Jorge
On Wed, Dec 07, 2005 at 10:21:10AM +0100, Plm, Rdiger, VIS wrote:
I would like to set the c-aborted in mod_proxy's proxy_handler after the
run_scheme_handler.
Reason:
1. We can define a clear interface for the scheme handlers here:
If the backend broke before you sent headers just
On Wed, Dec 07, 2005 at 03:48:39PM -, [EMAIL PROTECTED] wrote:
+* proxy_util: Fix case where a shared keepalive connection results in
+ different (and incorrect) workers from being accessed.
+
-Ursprüngliche Nachricht-
Von: Justin Erenkrantz
Gesendet: Mittwoch, 7. Dezember 2005 17:08
An: dev@httpd.apache.org
Betreff: Re: 2.2 mod_http_proxy and partial pages
[..cut..]
Feel free to commit a patch. =)
I will do so :).
2. I am not 100% percent happy with the
On Wed, Dec 07, 2005 at 05:24:46PM +0100, Plm, Rdiger, VIS wrote:
Yes, I know. Maybe this is nitpicking, but my original understanding is that
c-aborted is set if the connection to the client has broken for whatever
external
reason on the network route between client and server, not if we
Justin Erenkrantz wrote:
On Wed, Dec 07, 2005 at 03:48:39PM -, [EMAIL PROTECTED] wrote:
+* proxy_util: Fix case where a shared keepalive connection results in
+ different (and incorrect) workers from being accessed.
+
On Wed, Dec 07, 2005 at 11:29:57AM -0500, Jim Jagielski wrote:
The sole reason was the keep the present setup, so that if
is_address_reusable becomes more accurate we don't loose
information on what was the original intent... I'd also
Can you please elaborate on that? Thanks. -- justin
Jim Jagielski wrote:
Justin Erenkrantz wrote:
On Wed, Dec 07, 2005 at 03:48:39PM -, [EMAIL PROTECTED] wrote:
+* proxy_util: Fix case where a shared keepalive connection results in
+ different (and incorrect) workers from being accessed.
+
Justin Erenkrantz wrote:
On Wed, Dec 07, 2005 at 11:29:57AM -0500, Jim Jagielski wrote:
The sole reason was the keep the present setup, so that if
is_address_reusable becomes more accurate we don't loose
information on what was the original intent... I'd also
Can you please elaborate
-Ursprüngliche Nachricht-
Von: Justin Erenkrantz
Gesendet: Mittwoch, 7. Dezember 2005 17:30
An: dev@httpd.apache.org
Betreff: Re: 2.2 mod_http_proxy and partial pages
On Wed, Dec 07, 2005 at 05:24:46PM +0100, Plm, Rdiger, VIS wrote:
[..cut..]
Nope, that's the flag we set
-Ursprüngliche Nachricht-
Von: Jim Jagielski
Gesendet: Mittwoch, 7. Dezember 2005 17:43
An: Justin Erenkrantz
Cc: dev@httpd.apache.org; [EMAIL PROTECTED]
Betreff: Re: svn commit: r354779 - /httpd/httpd/branches/2.2.x/STATUS
Sure... Right now, there appears to be some questions
=?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VIS?= wrote:
-Urspr=FCngliche Nachricht-
Von: Jim Jagielski=20
Gesendet: Mittwoch, 7. Dezember 2005 17:43
An: Justin Erenkrantz
Cc: dev@httpd.apache.org; [EMAIL PROTECTED]
Betreff: Re: svn commit: r354779 -
Configuration .. make it configurable. by that I mean allowing people to
use LDAP or a DB to hold the configuration files, and not a flat file.
This is mainly intended for large server farms. Currently the main
reason for logging onto a webserver is to change it's configuration (and
bounce)
Brandon Fosdick wrote:
Would it be possible to use something like fam (or kqueue on FreeBSD) and
have httpd notified whenever the config file changes? That would solve
part of the above desire without requiring the extensive changes needed to
go to a db/ldap system.
That could be external to
Brandon Fosdick wrote:
Would it be possible to use something like fam (or kqueue on FreeBSD)
and
have httpd notified whenever the config file changes? That would solve
part of the above desire without requiring the extensive changes needed
to
go to a db/ldap system.
That could be
On Dec 7, 2005, at 2:01 PM, Brandon Fosdick wrote:
Configuration .. make it configurable. by that I mean allowing
people to
use LDAP or a DB to hold the configuration files, and not a flat
file.
This is mainly intended for large server farms. Currently the main
reason for logging onto a
That could be external to httpd. Just have a monitor (or in cfengine,
or whatever) that when the config changes it issues a graceful restart.
Simple and straight-forward.
Oops, I made a typo, and pressed save. poof there goes my website!
IMO, it's a bad idea to automagically restart when
On 12/07/2005 08:18 PM, Brandon Fosdick wrote:
Brandon Fosdick wrote:
[..cut..]
And, to me at least, it seems Intuitively Correct that an app should be
watching it's own config files for changes and then responding
appropriately. I see this as being in the same vein as re-reading config
Just a short reminder. I just got the 3rd duplicate for PR37145
( data loss with httpd-2.0.55 reverse proxy method=post) and I remember myself
that there had been additional cases that had been reported on the list.
The patch is currently missing one vote for backport to 2.0.x.
I know that 2.0.56
On Dec 7, 2005, at 3:04 PM, Joost de Heer wrote:
That could be external to httpd. Just have a monitor (or in
cfengine,
or whatever) that when the config changes it issues a graceful
restart.
Simple and straight-forward.
Oops, I made a typo, and pressed save. poof there goes my
does this problem effect 2.0.55 too?
-Ursprüngliche Nachricht-
Von: Ruediger Pluem [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 7. Dezember 2005 21:44
An: dev@httpd.apache.org
Betreff: PR 37145
Just a short reminder. I just got the 3rd duplicate for PR37145
( data loss with
Okay, so what is the status of this? Are the two patches submitted
good enough for all those concerned.
AFAIK, they seem to fix my issue. I would like some idea of how 2.2.1
will handle it, so I do not wind up having to patch and re-patch here.
TIA
--
Brian Akins
Lead Systems Engineer
CNN
On 12/07/2005 09:48 PM, Matthias Behrens wrote:
does this problem effect 2.0.55 too?
AFAIK it does only affect 2.0.55 of the stable releases.
It is a regression from 2.0.54 caused by the very much
needed changes to mod_proxy to fix CVE-2005-2088.
Regards
Rüdiger
On Wed, Dec 07, 2005 at 11:01:35AM -0800, Brandon Fosdick wrote:
Would it be possible to use something like fam (or kqueue on FreeBSD) and
have httpd notified whenever the config file changes?
We could do the SIGIO trick which diablo does on BSD, though the problem
there is that on other
Joost de Heer wrote:
That could be external to httpd. Just have a monitor (or in cfengine,
or whatever) that when the config changes it issues a graceful restart.
Simple and straight-forward.
Oops, I made a typo, and pressed save. poof there goes my website!
IMO, it's a bad idea to
On Dec 7, 2005, at 8:44 AM, Plüm, Rüdiger, VIS wrote:
Nope, that's the flag we set when we want the core to drop
the connection. I thought that it would be set by the filters
when a connection was dropped, but, as I said earlier in this
thread, I'm wrong. The filters will never ever set it. --
Hi,
I am trying to install Apache 2.0.54 on RedHat
enterprise edition, though the Installation is a succes, starting of Apache
results in lots of zombie processes with no active process.
Machine Information:
uname -a Linux ex07
2.4.21-37.EL #1 Wed Sep 7 13:35:21 EDT 2005 i686 i686 i386
Paul Querna wrote:
My intention is for this to be a wide open brainstorming thread.
I expect that we will be able to discuss several ideas in much more
detail at the Hackathon next week, but I really want to get all ideas
'on the table'.
Here's my list. Or at least, the partial list that
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2005-12-01 20:35:16 -0500 (Thu, 01 Dec 2005) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
Documentation status is
APACHE 2.3 STATUS: -*-text-*-
Last modified at [$Date: 2005-11-13 02:22:18 -0500 (Sun, 13 Nov 2005) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
Documentation status is maintained
-Ursprüngliche Nachricht-
Von: Roy T. Fielding
Gesendet: Donnerstag, 8. Dezember 2005 03:17
[..cut..]
Ok. Then I withdraw my objections against the setting of
c-aborted. I
just understood its purpose wrong. Thanks for clarification.
No, you understood its purpose
34 matches
Mail list logo
