RE: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
Is that always true? For example, expat is not compiled with those flags. -Original Message- From: Roy T. Fielding [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 29, 2001 7:08 PM To: [EMAIL PROTECTED] Subject: Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page As a side note, some portions of the code are compiled with -D_REENTRANT -D_THREAD_SAFE even when building using the prefork mpm. Why? Doesn't that have the potential to do the wrong thing on some platforms? No, it would do the wrong thing if they were not defined. They are required for the entire executable if any part of the exec has been compiled with those flags. In our case, since modules like PHP and others will be compiled with those flags, we must always compile with those flags or mod_php's return values for errno won't be correctly interpreted by the httpd core (a problem that was fixed in some version of 1.3.x by always setting those flags on platforms that support it). Roy
Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
William A. Rowe, Jr. wrote: I'll try reproducing on Win32. [Dang me for testing with IE! Mozilla from now on, promise!!! Whatever happened to that little 'show http headers' feature from Mozilla .91???] I dunno, but I have a tiny little VB utility to get HTTP headers without having to do the whole telnet thing. Lemme know if you want it. -- Jerry Baker PGP Key: http://www.jerrybaker.org/pgp.html LAME MP3 Encoder Binaries: http://www.jerrybaker.org/lame/ Apache 2.0 Web server Installer: http://www.jerrybaker.org/apache/
Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
As a side note, some portions of the code are compiled with -D_REENTRANT -D_THREAD_SAFE even when building using the prefork mpm. Why? Doesn't that have the potential to do the wrong thing on some platforms? No, it would do the wrong thing if they were not defined. They are required for the entire executable if any part of the exec has been compiled with those flags. In our case, since modules like PHP and others will be compiled with those flags, we must always compile with those flags or mod_php's return values for errno won't be correctly interpreted by the httpd core (a problem that was fixed in some version of 1.3.x by always setting those flags on platforms that support it). Roy
Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
On Wed, Aug 29, 2001 at 06:01:35PM -0700, Marc Slemko wrote: On Wed, 29 Aug 2001, Justin Erenkrantz wrote: On Wed, Aug 29, 2001 at 04:14:39PM -0600, Charles Randall wrote: Using the prefork mpm on FreeBSD 4.2-R with a default installation (./configure --prefix=/my/full/path -with-port=8080) a request for a non-existant page (E.g., /bogus) returns the HTML error document as text/plain. Yup, that's a bug. I don't *think* it is a showstopper though. I can Erm... it is a showstopper from making it beta, that's for sure. No big deal. Let's release it as an alpha. Cheers, -g -- Greg Stein, http://www.lyra.org/
Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
On Wed, 29 Aug 2001, Greg Stein wrote: On Wed, Aug 29, 2001 at 06:01:35PM -0700, Marc Slemko wrote: On Wed, 29 Aug 2001, Justin Erenkrantz wrote: On Wed, Aug 29, 2001 at 04:14:39PM -0600, Charles Randall wrote: Using the prefork mpm on FreeBSD 4.2-R with a default installation (./configure --prefix=/my/full/path -with-port=8080) a request for a non-existant page (E.g., /bogus) returns the HTML error document as text/plain. Yup, that's a bug. I don't *think* it is a showstopper though. I can Erm... it is a showstopper from making it beta, that's for sure. No big deal. Let's release it as an alpha. This is a problem simply with the multi-language error-docs. If you want to go beta, just comment them out of the default config file. I doubt very much else will be hit by this problem. Joshua.
Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
On Wed, Aug 29, 2001 at 08:20:38PM -0700, Justin Erenkrantz wrote: HEAD looks like it has this problem fixed (the buffered read fixes perhaps?). Please check it out and see if it works for you with the latest CVS. No, it's not fixed. My bad. I had a stale config which had SetOutputFilter instead of AddOutputFilter for the error pages. What does SetOutputFilter do that AddOutputFilter doesn't? I'm drilling down to see what's up. -- justin
Re: 2.0.25 on FreeBSD 4.2-R -- 404 returns text/plain error page
From: Justin Erenkrantz [EMAIL PROTECTED] Sent: Wednesday, August 29, 2001 10:29 PM On Wed, Aug 29, 2001 at 08:20:38PM -0700, Justin Erenkrantz wrote: HEAD looks like it has this problem fixed (the buffered read fixes perhaps?). Please check it out and see if it works for you with the latest CVS. No, it's not fixed. My bad. I had a stale config which had SetOutputFilter instead of AddOutputFilter for the error pages. What does SetOutputFilter do that AddOutputFilter doesn't? I'm drilling down to see what's up. -- justin Nothing that Apache hasn't done forever (incorrectly) :( Patch in 3 minutes.