[about:config feature] Bypass proxy setting for WebSocket

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
jangdonggun1234
Fanatic
Fanatic
Posts: 104
Joined: 2013-06-06, 01:29

[about:config feature] Bypass proxy setting for WebSocket

Unread post by jangdonggun1234 » 2016-01-29, 21:31

I think we can consider adding a about:config to prevent Websocket from using http/https proxy, because:
- Many web proxies still don't have websocket support yet, the result is proxy users won't be able to use Websocket service Microsoft's Virtual Labs ( https://dpetechnet.cloudapp.net/Home.aspx ), games based on WebSocket, and this WebSocket test will fail ( http://www.websocket.org/echo.html )
- And not only remote proxy servers, transparent proxy servers like Proxidomo ( https://github.com/amate/Proxydomo/ ), Proximitron, Polipo, HandyCache cannot play with WebSocket too, and those transparent proxies are very useful.
- I think we should love WebSocket more because it is becoming better and better day after day, for example remote destop service, many useful service based on WebSocket

My idea:
- If we enable this about:config key, Palemoon will check if HTTP header contain Websocket's unique headers like "Upgrade: websocket" or "Connection: Upgrade" or "Sec-WebSocket-Key" or "Sec-WebSocket-Protocol" or "Sec-WebSocket-Version", and if one of those HTTP headers is present then we will ignore Palemoon's proxy setting for this request

dark_moon

Re: [about:config feature] Bypass proxy setting for WebSocket

Unread post by dark_moon » 2016-01-30, 00:41

Uhm whats with that about:config setting. Not enough?
websocket.png

jangdonggun1234
Fanatic
Fanatic
Posts: 104
Joined: 2013-06-06, 01:29

Re: [about:config feature] Bypass proxy setting for WebSocket

Unread post by jangdonggun1234 » 2016-01-30, 06:09

dark_moon wrote:Uhm whats with that about:config setting. Not enough?
websocket.png
That config will completely disable WebSocket, that mean even without non-Websocket supported web proxy we won;t be able to use WebSocket...

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35476
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: [about:config feature] Bypass proxy setting for WebSocket

Unread post by Moonchild » 2016-01-31, 01:56

This would be a problem with the proxy in use, not a problem with Pale Moon.

Mixing proxy and non-proxy connections is likely not going to work, to begin with, since the server would get websocket connections from a different IP than web traffic (which any half-decent webserver would block for security reasons). It's just a bad idea and combating symptoms of incomplete proxy implementations rather than doing it properly. Thanks for the suggestion but I'm going to have to reject this idea.

What you need is a proxy that supports websockets. Plain and simple.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Locked