Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3DF4C24F.1000005@feld.cvut.cz>
Date: Mon, 09 Dec 2002 17:18:23 +0100
From: Pavel Novy <novy@feld.cvut.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.2) Gecko/20021126
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: [PATCH] ap_default_port() and Apache 1.3 on NetWare
References: <3DF46CD6.9030001@feld.cvut.cz>
 <p05200f05ba1a61061ec8@[209.133.211.10]>
In-Reply-To: <p05200f05ba1a61061ec8@[209.133.211.10]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jim Jagielski wrote:
> At 11:13 AM +0100 12/9/02, Pavel Novy wrote:
> 
>>Port 443 is not treated as a default port for the https method on
>>NetWare, so wrong redirects like this are occuring:
>>
>>"https://server_name/some_location" (missing a trailing slash)
>>-> "https://server_name:443/some_location/"
>>
> 
> 
> Pavel, how is the above redirect wrong? Or do you mean you'd prefer
> the redirect simply not add the port information (though it is correct)?
> 

I think it's abnormal behaviour of Apache to switch from "server" to 
"server:port" (add port) in such cases, when port number is default for 
scheme. I never seen this for "http" scheme (tested on Linux and 
NetWare), the same for "https" on Linux. Why for "https" on NetWare?
Not absolutely sure, but it seems it doesn't matter here what 
UseCanonicalName is set to.

Also, when accessing a page like "https://someserver/someplace" and such 
place is protected, user is asked twice for authentication credentials 
(once for "server", once for "server:443"). It's not right, though. In 
fact, such bahaviour may vary depending on browser used to access the 
page...

Pavel