Missing proxy configuration support in WebSocket API

[glassfishrobot]

Currently there is no spec defined mechanism for providing proxy configurations when ClientEndpoint is behind a http proxy. There are multiple variations of implementations but still such configuration could be interfaced in spec defined way so that connectToServer methods in WebSocketContainer respect that.

Affected Versions

[1.0]

[glassfishrobot]

@glassfishrobot Commented
Reported by nickytd

[glassfishrobot]

@glassfishrobot Commented
markt_asf said:
java.net.ProxySelector looks to be the best way to do this at the moment. It is pluggable and falls back to the system properties.

The main question is should the URI passed to it be ws/wss or http/https?

ws/wss
Pros - allows different proxies to be used for web socket and http connections
Cons - not currently supported by ProxySelector

http/https
Cons - does not allow for different proxies for web socket and http
Pros - currently supported by ProxySelector

There is currently no way to differentiate between a "scheme not supported" response and an explicit "don't use a proxy for that scheme" response. Differentiation between the two would require a custom ProxySelector.

I'm leaning towards ws/wss and requiring a custom ProxySelector as that allows for a clear distinction between WebSocket and HTTP traffic.

[glassfishrobot]

@glassfishrobot Commented
markt_asf said:
Having had 2+ years to reflect on this and to see how proxies have developed I've changed my mind on this. Using the http proxy settings for WebSocket should be fine.

[glassfishrobot]

@glassfishrobot Commented
nickytd said:
Is there a related discussion on the JSR spec group?

[glassfishrobot]

@glassfishrobot Commented
markt_asf said:
No. This is just my personal opinion and what I intend to implement for Tomcat.

[glassfishrobot]

@glassfishrobot Commented
nickytd said:
+1 I think I should have a patch somewhere using java.net.ProxySelector if I remember correctly ...

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA WEBSOCKET_SPEC-202

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/websocket-spec/issues/202
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @pavelbucek