Since the SSL support for NetWare is handled by the OS rather than through MOD_SSL, determining the default port for a request needs to be handled differently. NetWare already handled part of this by implementing ap_http_method() to actually ask Winsock what http method was being used rather than hard coding it to "http". Apparently we forgot to also allow ap_default_port() to also ask rather than hard coding "80". I will be committing this patch shortly. Thanks Pavel.
Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] Monday, December 09, 2002 9:18:23 AM >>> 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
