Closed
Bug 1460879
Opened 8 years ago
Closed 7 years ago
Non-secure WebSocket through proxy that does not support Upgrade fails
Categories
(Core :: Networking: WebSockets, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: niels, Unassigned)
Details
(Whiteboard: [necko-triaged])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180503143129
Steps to reproduce:
Connect to the Internet through a HTTP/HTTPS proxy server that does not natively support websockets, in my case: Squid.
Visit a website that uses non-secure (ws://) websockets, e.g. speedtest.net.
Actual results:
Firefox translates the websocket requests to HTTP GET requests (with Upgrade headers, etc). This does not work because the proxy does not understand that it's supposed to upgrade the connection.
Expected results:
Firefox should translate the websocket requests (ws://) to HTTP CONNECT requests, just like it does for secure websocket requests (wss://) and as is suggested in rfc6455.
|
||
Updated•7 years ago
|
Component: Untriaged → Networking: WebSockets
Product: Firefox → Core
|
||
Updated•7 years ago
|
Flags: needinfo?(michal.novotny)
|
||
Updated•7 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(michal.novotny)
Priority: -- → P3
Whiteboard: [necko-triaged]
|
|
||
Comment 1•7 years ago
|
||
This already works as expected. The reason why it fails in your case is probably that squid doesn't allow to use CONNECT method for port 80. By default it allows connecting only to port 443.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•