"Jeffrey W. Baker" wrote:
> 
> A fix was committed for 83401 into the Mozilla tree.  I'm looking at the
> diffs and it looks like this will prevent Mozilla from contacting an HTTP
> server that listens on a well known port other than 80, such as 25 or 389.
>  What business is it of Mozilla's that my HTTP server is on port 25?
>  Suppose my secure IMAP server really is on the finger port.  I want
> Mozilla to work in those cases.  If I say the url is
> https://www.myhost.com:143/path, I expect Mozilla to go get the URL from
> that host, on that port, and using that protocol.  I do not expect Mozilla
> to drop my request because of an internal blacklist.

There seem to be problems with URLs like this:
ftp://%0a<SMTP commands here>@host:25

Clarence

Reply via email to