168753 - url bar badly parsed if protocol is omitted and a port is specified

Status: RESOLVED DUPLICATE of bug 155344

(SeaMonkey :: Location Bar, defect)

Description

[Ian Batterbee]

For example, if I go to "mybox:80", I expect mozilla to interpret that as a
request to use the http protocol to connect to host 'mybox' on port 80.

What happens is that mozilla thinks that mybox is a protocol name, and comes up
with a message box saying "mybox is not a registered protocol".

If I leave out the port number, and just type "mybox" in the url bar, mozilla
correctly assumes http://, but when I specify a port to connect on, it no longer
makes that assumption.

This behaviour is inconsistant, if nothing else, and I'm pretty sure I could
type just a hostname and port in netscape 4.x.

Comment 1

[Ian Neal]

*** This bug has been marked as a duplicate of 155344 ***