1154331 - Connection to secured websocket goes to wrong port

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect)

Description

[Andy]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150402191859

Steps to reproduce:

I payed with a simplest websocket echo application. Everithing working fine with unsecured websockets ("ws://"), but then I switched to secured websockets and try to connect to secured websocket:

webSocket = new WebSocket("wss://localhost:8443/wss-web_war/echo");

(please note port 8443).


Actual results:

If script is being loaded from the net, then FF complains it can't connect to wss://localhost:8080/wss-web_war/echo
(please note port 8080 here!).
But if I manually copy-paste line webSocket = new WebSocket("wss://localhost:8443/wss-web_war/echo"); into a console, then everything works fine.


Expected results:

Both calls should succseeds, regardless of origin: net or console.
I also try the same script in Chrome and it works fine in it.

Comment 1

[Boris Zbarsky [:bzbarsky]]

> then FF complains it can't connect to wss://localhost:8080/wss-web_war/echo

Is it possible you have an old version of the script cached?

Comment 2

[Andy]

(In reply to Not doing reviews right now from comment #1)
> > then FF complains it can't connect to wss://localhost:8080/wss-web_war/echo
> 
> Is it possible you have an old version of the script cached?

Ooops.. Yes, looks like it was an issue.

Comment 3

[Boris Zbarsky [:bzbarsky]]

OK.  Is there still a Gecko bug here?  ;)

Comment 4

[Andy]

(In reply to Not doing reviews right now from comment #3)
> OK.  Is there still a Gecko bug here?  ;)

No :) What is the right process? Do I have to mark it as resoled or is there a way to mark it as not a bug at all?

Comment 5

[Boris Zbarsky [:bzbarsky]]

Just gets resolved invalid.  Thanks for the quick followup!