UseCanonicalName Off

2004-05-07 Thread Jim Jagielski
In the 2.1 STATUS file we see: * When UseCanonicalName is set to OFF, allow ap_get_server_port to check r-connection-local_addr-port before defaulting to server-port or ap_default_port() This is, in fact, the behavior in 1.3.31... The idea being that with UseCanonicalName Off, we

UseCanonicalName Off *surprise*

2003-12-19 Thread William A. Rowe, Jr.
conform to the Host header provided by the client... UseCanonicalName On -or- UseCanonicalName Off, but the Host: header was missing (e.g. HTTP/1.0) In 1.3 - the host's {ServerName}:{Port} is returned. In 2.0 - the host {Servername} is returned (must include port suffix). there were

Re: UseCanonicalName Off *surprise*

2003-12-19 Thread Tony Finch
On Fri, Dec 19, 2003 at 10:04:15AM -0600, William A. Rowe, Jr. wrote: UseCanonicalName Off, Host: header provided (HTTP/1.1) The host name header *excluding the host header port suffix * of the request is concatenated to httpd 1.3's Port directive setting or the real port number

Re: UseCanonicalName Off *surprise*

2003-12-19 Thread Jim Jagielski
A. Rowe, Jr. wrote: UseCanonicalName On -or- UseCanonicalName Off, but the Host: header was missing (e.g. HTTP/1.0) In 1.3 - the host's {ServerName}:{Port} is returned. In 2.0 - the host {Servername} is returned (must include port suffix). there were no surprises there. UseCanonicalName Off

Re: UseCanonicalName Off *surprise*

2003-12-19 Thread William A. Rowe, Jr.
At 11:16 AM 12/19/2003, Tony Finch wrote: On Fri, Dec 19, 2003 at 10:04:15AM -0600, William A. Rowe, Jr. wrote: UseCanonicalName Off, Host: header provided (HTTP/1.1) The host name header *excluding the host header port suffix * of the request is concatenated to httpd 1.3's Port

Re: UseCanonicalName Off *surprise*

2003-12-19 Thread Brian Akins
William A. Rowe, Jr. wrote: UseCanonicalName Off Listen 8080 Port 80 an inbound request with a Host header of foo:80 would respond with the redirection http://foo:80/ It does not. The Listen port again applies until you turn UseCanonicalName On. We had something similar. What we did that works

Re: UseCanonicalName Off *surprise*

2003-12-19 Thread Jim Jagielski
On Dec 19, 2003, at 1:35 PM, William A. Rowe, Jr. wrote: Let me be clear (on the 1.3 side)... one expects that given; UseCanonicalName Off Listen 8080 Port 80 an inbound request with a Host header of foo:80 would respond with the redirection http://foo:80/ It does not. The Listen port again

Re: UseCanonicalName Off *surprise*

2003-12-19 Thread Jim Jagielski
Brian Akins wrote: We had something similar. What we did that works is: UseCanonicalName On Listen 80 Listen 8080 ServerName www.domain.com:80 So redirects, no matter what port they came in one, get redirected to port 80. This was our desired effect. Under 1.3?? --

UseCanonicalName Off in default config

2002-02-12 Thread Joshua Slive
constructs self-referencing +# URLs and the SERVER_NAME and SERVER_PORT variables. +# When set Off, Apache will use the Hostname and Port supplied +# by the client. When set On, Apache will use the value of the +# ServerName directive. # -UseCanonicalName On +UseCanonicalName Off

Re: UseCanonicalName Off in default config

2002-02-12 Thread Martin Kraemer
On Tue, Feb 12, 2002 at 03:11:52PM -0500, Joshua Slive wrote: This configuration seems more idiot-proof and would eliminate a huge chunk of newbie why can't I access a directory without a trailing slash questions. I'm posting here before committing because I don't know if there may be some