You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Greg Ames <gr...@remulak.net> on 2001/11/08 00:46:07 UTC

daedalus is running 2.0.28-dev

...as of Wednesday, 07-Nov-2001 15:02:05 PST .  This is HEAD from around
noon EST today.  It has a fix for yesterday's loops with truncated
request bodies and other goodness.

Let us know if you spot anything odd.  I did more config file editing
than normal, due to being over-zealous about cleaning up old
directories.  The changes to bring the 2.0.24 config up to date are:

1. change Port to Listen
2. add MultiviewsMatch Handler so .asis files work as expected
3. remove the $ from <Files ~ "\.html$"> so we match .html.en, .html.fr,
etc., and
4. turn off mod_mime_magic

plus the usual directory changes.  The first three above might be
material for a 1.3 -> 2.0 config migration guide.  Better yet, #2 should
be the default so we have less explaining to do.

Greg

Re: daedalus is running 2.0.28-dev [Connection: headers?]

Posted by "Roy T. Fielding" <fi...@ebuilt.com>.
On Thu, Nov 08, 2001 at 12:57:28PM +0100, Martin Kraemer wrote:
> The "hangs" I observed are a squid/ICS problem. That's what I found out
> by bypassing squid and using a different proxy. However, I don't know
> what actually causes squid to hang in this request only. Tcpdump
> shows that it gets the response all right. Dunno. It's definitely
> the combo of
>   client <--> squid <--> ICS proxy <--> www.apache.org
> which causes squid to hang. Apache seems to be abolutely correct wrt RFC2616.

Is the client sending the non-standard proxy-keepalive option on the request?
That can cause proxy chains to hang if one of them makes the mistake of
honoring it.

....Roy


Re: daedalus is running 2.0.28-dev [Connection: headers?]

Posted by Martin Kraemer <Ma...@Fujitsu-Siemens.com>.
The "hangs" I observed are a squid/ICS problem. That's what I found out
by bypassing squid and using a different proxy. However, I don't know
what actually causes squid to hang in this request only. Tcpdump
shows that it gets the response all right. Dunno. It's definitely
the combo of
  client <--> squid <--> ICS proxy <--> www.apache.org
which causes squid to hang. Apache seems to be abolutely correct wrt RFC2616.

   Martin
-- 
<Ma...@Fujitsu-Siemens.com>         |     Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730  Munich,  Germany

Re: daedalus is running 2.0.28-dev

Posted by Greg Ames <gr...@remulak.net>.
Joshua Slive wrote:
> 
> > From: gregames@Mail.MeepZor.Com [mailto:gregames@Mail.MeepZor.Com]On
> 
> > 1. change Port to Listen
> > 2. add MultiviewsMatch Handler so .asis files work as expected
> > 3. remove the $ from <Files ~ "\.html$"> so we match .html.en, .html.fr,
> > etc., and
> > 4. turn off mod_mime_magic
> >
> > plus the usual directory changes.  The first three above might be
> > material for a 1.3 -> 2.0 config migration guide.  Better yet, #2 should
> > be the default so we have less explaining to do.
> >
> 
> There is such a guide:
> http://httpd.apache.org/docs-2.0/upgrading.html
> but it is rather out of date.  There are tons (well, a bunch) of changes
> that have not been documented at all, including 1 and 2 above.  

Actually, #1 is documented there.  Thanks for the pointer.

>                                                                 3 doesn't
> need to be documented by in the upgrading guide because the server-parsed
> handler still exists for backward-compatibility.

I guess that leaves #2.  I'll see about making it the default. 

Greg

RE: daedalus is running 2.0.28-dev

Posted by Joshua Slive <jo...@slive.ca>.
> From: Joshua Slive [mailto:joshua@slive.ca]

> There is such a guide:
> http://httpd.apache.org/docs-2.0/upgrading.html
> but it is rather out of date.  There are tons (well, a bunch) of changes
> that have not been documented at all, including 1 and 2 above.  3 doesn't
> need to be documented by in the upgrading guide because the server-parsed
> handler still exists for backward-compatibility.

Sorry, I take that back.  Port/Listen is correctly documented and
MultiviewsMatch is documented but not in upgrading.

Joshua.




---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


RE: daedalus is running 2.0.28-dev

Posted by Joshua Slive <jo...@slive.ca>.
> From: gregames@Mail.MeepZor.Com [mailto:gregames@Mail.MeepZor.Com]On

> 1. change Port to Listen
> 2. add MultiviewsMatch Handler so .asis files work as expected
> 3. remove the $ from <Files ~ "\.html$"> so we match .html.en, .html.fr,
> etc., and
> 4. turn off mod_mime_magic
>
> plus the usual directory changes.  The first three above might be
> material for a 1.3 -> 2.0 config migration guide.  Better yet, #2 should
> be the default so we have less explaining to do.
>

There is such a guide:
http://httpd.apache.org/docs-2.0/upgrading.html
but it is rather out of date.  There are tons (well, a bunch) of changes
that have not been documented at all, including 1 and 2 above.  3 doesn't
need to be documented by in the upgrading guide because the server-parsed
handler still exists for backward-compatibility.

Joshua.


RE: daedalus is running 2.0.28-dev

Posted by Joshua Slive <jo...@slive.ca>.
> From: gregames@Mail.MeepZor.Com [mailto:gregames@Mail.MeepZor.Com]On

> 1. change Port to Listen
> 2. add MultiviewsMatch Handler so .asis files work as expected
> 3. remove the $ from <Files ~ "\.html$"> so we match .html.en, .html.fr,
> etc., and
> 4. turn off mod_mime_magic
>
> plus the usual directory changes.  The first three above might be
> material for a 1.3 -> 2.0 config migration guide.  Better yet, #2 should
> be the default so we have less explaining to do.
>

There is such a guide:
http://httpd.apache.org/docs-2.0/upgrading.html
but it is rather out of date.  There are tons (well, a bunch) of changes
that have not been documented at all, including 1 and 2 above.  3 doesn't
need to be documented by in the upgrading guide because the server-parsed
handler still exists for backward-compatibility.

Joshua.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org