2.0.54 release candidate tarball available for testing

Hi, As usual the tarballs are at: http://httpd.apache.org/dev/dist/ Please give 2.0.54 a whirl and report any problems (or successes) ;) Thanks, Sander

Re: 2.0.54 release candidate tarball available for testing

On Tue, Apr 12, 2005 at 09:25:22AM +0200, Sander Striker wrote: Hi, As usual the tarballs are at: http://httpd.apache.org/dev/dist/ Please give 2.0.54 a whirl and report any problems (or successes) ;) +1 for release, looks good in httpd-test'ing here. Thanks for RMing. joe

Re: 2.0.54 release candidate tarball available for testing

tisdag 12 april 2005 09.25 skrev Sander Striker: Hi, As usual the tarballs are at: http://httpd.apache.org/dev/dist/ Please give 2.0.54 a whirl and report any problems (or successes) ;) Works for me. +1 -- Regards // Oden Eriksson Mandriva: http://www.mandriva.com NUX: http://nux.se

Re: 2.0.54 release candidate tarball available for testing

At 02:25 AM 4/12/2005, Sander Striker wrote: As usual the tarballs are at: http://httpd.apache.org/dev/dist/ Please give 2.0.54 a whirl and report any problems (or successes) ;) Hmmm. How does the current infrastructure state of http://*.apache.org fit into testing this live for our site?

Re: 2.0.54 release candidate tarball available for testing

William A. Rowe, Jr. wrote: At 02:25 AM 4/12/2005, Sander Striker wrote: As usual the tarballs are at: http://httpd.apache.org/dev/dist/ Please give 2.0.54 a whirl and report any problems (or successes) ;) Hmmm. How does the current infrastructure state of http://*.apache.org fit into testing

Re: 2.0.54 release candidate tarball available for testing

William A. Rowe, Jr. wrote: At 02:25 AM 4/12/2005, Sander Striker wrote: As usual the tarballs are at: http://httpd.apache.org/dev/dist/ Please give 2.0.54 a whirl and report any problems (or successes) ;) Hmmm. How does the current infrastructure state of http://*.apache.org fit into testing

ajax (most of *.apache.org) now running httpd 2.0.54 pre-release

As the subject says... Let me know if you see any problems. Joshua.

Re: 2.0.54 release candidate tarball available for testing

At 09:16 AM 4/12/2005, Bill Stoddard wrote: William A. Rowe, Jr. wrote: Hmmm. How does the current infrastructure state of http://*.apache.org fit into testing this live for our site? Is it possible to subject ourselves to the usual three days of our own dogfood? +1 I ask because - with some

Single-threaded/non-blocking frontend and multi-threaded/processed backend

Hi, I originally posted this feature request to the bug tracker, but Joe Orton suggested it'd post it here instead, so here it is. I'd like to see a new 'MPM' that basically works like this: A single or few-threaded, non-blocking frontend that accepts incoming connections, receives requests and

ssi debug extension??

Hi to all, I'm new to this mailinglist :) I'm a young developer (started many years ago, but the big step (unix world!) only a few months ago..) and I'm currently working for a big web-company.. We use apache (oooh) as webserver, and this is the point: we need to trace all the SSI calls, in order

ap_method_list_do?

This code was added in 2001, and it has never done anything. Here, Look at body of the ap_method_list_vdo in modules/http/http_protocol.c: { } Yes. There is nothing inside the function. The Associated svn log: r88453 | rbb | 2001-03-04 20:43:56 -0800 (Sun, 04 Mar 2001) | 4 lines Another chunk of

Re: Single-threaded/non-blocking frontend and multi-threaded/processed backend

Olaf van der Spek wrote: Hi, I originally posted this feature request to the bug tracker, but Joe Orton suggested it'd post it here instead, so here it is. I'd like to see a new 'MPM' that basically works like this: A single or few-threaded, non-blocking frontend that accepts incoming