Re: Tagged 2.0

2003-09-17 Thread Jeff Trawick
Sander Striker wrote: I've re tagged the 2.0 tree with STRIKER_2_0_48_PRE2. I've put some tarballs containing that tag up at: There are some other fixes merged back since then, and it looks like another set of fixes that are close to being approved. Here is one issue I'd strongly suggest

RE: Tagged 2.0

2003-09-17 Thread Sander Striker
From: Jeff Trawick [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2003 2:15 PM Sander Striker wrote: I've re tagged the 2.0 tree with STRIKER_2_0_48_PRE2. I've put some tarballs containing that tag up at: There are some other fixes merged back since then, and it looks like

Re: cvs commit: apache-1.3/src/main rfc1413.c

2003-09-17 Thread William A. Rowe, Jr.
At 04:54 PM 9/16/2003, Brad Nicholes wrote: Looking through the code I don't see anything that would be a thread-safety issue. What am I missing? /* rfc1413 - return remote user name, given socket structures */ API_EXPORT(char *) ap_rfc1413(conn_rec *conn, server_rec *srv) { static char

Re: cvs commit: apache-1.3/src/main rfc1413.c

2003-09-17 Thread Brad Nicholes
Ah yeah, I noticed the problem with the JMP_BUF but for some reason I missed the local statics. I am assuming that these local variables are static simply to accomodate the setjmp() call. If I get rid of setjmp() and simply set the recv/send timeouts on the socket itself, there shouldn't be any

Re: cvs commit: apache-1.3/src/main rfc1413.c

2003-09-17 Thread William A. Rowe, Jr.
At 01:09 PM 9/17/2003, Brad Nicholes wrote: Ah yeah, I noticed the problem with the JMP_BUF but for some reason I missed the local statics. I am assuming that these local variables are static simply to accomodate the setjmp() call. If I get rid of setjmp() and simply set the recv/send timeouts

Re: cvs commit: apache-1.3/src/main rfc1413.c

2003-09-17 Thread Brad Nicholes
Sorry about the ugly .diff file. Forgot to add the -u when I did the diff. I already caught the trashed stack variable and made the fix so everything looks much better in the log (real info instead of trash). I also believe that Apache is smart enough not to make the call on a keep-alive.

Sync to CVS problem

2003-09-17 Thread Juan Rivera
Title: Sync to CVS problem Hi, I have previously downloaded a copy of the Apache server code from the cvs repository using "anoncvs" login and CVSROOT=:pserver:[EMAIL PROTECTED]:/home/cvspublic. However, I am unable to connect to the server for the past couple of days. I get the following

Re: Sync to CVS problem

2003-09-17 Thread Cliff Woolley
On Wed, 17 Sep 2003, Juan Rivera wrote: I have previously downloaded a copy of the Apache server code from the cvs repository using anoncvs login and CVSROOT=:pserver:[EMAIL PROTECTED]:/home/cvspublic. However, I am unable to connect to the server for the past couple of days. I get the

Re: cvs commit: apache-1.3/src/main rfc1413.c

2003-09-17 Thread William A. Rowe, Jr.
If you will change the logic for multithreads (not to be confused with your logic changes for winsock :-) from #if (defined(NETWARE) || defined(WIN32)) to use #ifdef MULTITHREAD and decorate STATIC (e.g. RFC_USER_STATIC) to avoid possible name clashes - I'd be very happy to accept this patch

Re: cvs commit: apache-1.3/src/main rfc1413.c

2003-09-17 Thread Brad Nicholes
No problem. How's this? Brad Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com [EMAIL PROTECTED] Wednesday, September 17, 2003 1:18:49 PM If you will change the logic for multithreads (not to be confused with your logic

Input filter and setting HTTP headers in Apache 2.0

2003-09-17 Thread albertochan
Hi, I am writing a module need to be able to examine POST data, and insert inbound HTTP request headers after my code has been run by apache so that: 1. the web application can still retrieve the POST data if required for its own consumption 2. the web application needs to have access

Reviewers wanted for second edition of Apache Pocket Reference

2003-09-17 Thread Andrew Ford
I am hoping to get a second edition of the Apache Pocket Reference together for O'Reilly by the end of November and wondered whether anyone out there would like to act as technical reviewer for the new edition? (This edition will of course cover Apache version 2 as well as 1.3.) I would also

[STATUS] (apache-1.3) Wed Sep 17 23:45:13 EDT 2003

2003-09-17 Thread Rodent of Unusual Size
APACHE 1.3 STATUS: -*-text-*- Last modified at [$Date: 2003/09/02 20:10:36 $] Release: 1.3.29-dev: In development 1.3.28: Tagged July 16, 2003. 1.3.27: Tagged September 30, 2002. Announced Oct 3, 2002. 1.3.26: Tagged June 18, 2002.

[STATUS] (httpd-2.0) Wed Sep 17 23:45:19 EDT 2003

2003-09-17 Thread Rodent of Unusual Size
APACHE 2.0 STATUS: -*-text-*- Last modified at [$Date: 2003/09/17 10:53:32 $] Release: 2.0.48 : in development 2.0.47 : released July 09, 2003 as GA. 2.0.46 : released May 28, 2003 as GA. 2.0.45 : released April 1, 2003 as GA.

[STATUS] (httpd-2.1) Wed Sep 17 23:45:28 EDT 2003

2003-09-17 Thread Rodent of Unusual Size
APACHE 2.1 STATUS: -*-text-*- Last modified at [$Date: 2003/08/31 16:14:38 $] 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