Thom May wrote:
+1 from Linux: prefork/perchild/threadpool/worker all build
prefork/worker both work fine in production environments.
The new httpd is looking good on www.apache.org (minotaur) since 09-Oct-2003
15:08:33 PDT. A few minutes before this, we had about a one minute outa
Thom May wrote:
+1 from Linux: prefork/perchild/threadpool/worker all build
prefork/worker both work fine in production environments.
+1 from me after testing worker on AIX 4.3.3, AIX 5.1, Solaris 8, HP-UX
11i, and Linux (UL 1.0), and refreshing my memory re: diffs between
APACHE_2
On Thu, 9 Oct 2003, fabio rohrich wrote:
Just sent an email to "[EMAIL PROTECTED]".
--Cliff
On Thu, 2003-10-09 at 12:48, André Malo wrote:
> The answer is simple: because it's not allowed, see RFC 2616, 14.30.
Thanks.
How do I detect that I got a malformed Host header? What does
ap_get_server_name do in this case? It seems to die
--
Brian Akins <[EMAIL PROTECTED]>
CNN Internet
Brian Akins wrote:
Stupid question.
not that ;-)
Why does mod_dir use ap_contruct_url when redirecting requests for
directories without a trailing "/"? Why doesn't it just do a relative
redirect?
The answer is simple: because it's not allowed, see RFC 2616, 14.30.
HTH, nd
Stupid question.
Why does mod_dir use ap_contruct_url when redirecting requests for
directories without a trailing "/"? Why doesn't it just do a relative
redirect?
We use a load balancer that uses alternative ports to direct traffic,
however, to the public, everything is port 80. We had to write
__
Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro
Anti-spam
http://it.yahoo.com/mail_it/foot/?http://it.mail.yahoo.com/
So, for now, users have to resort to
using this syntax (note the extra space):
The following patch fixes this little problem:
whee!
:)
--Geoff
+1 from Linux: prefork/perchild/threadpool/worker all build
prefork/worker both work fine in production environments.
