Bug 59758 - Add http proxy username-password credentials support for ClientEndpoint using system properties
Summary: Add http proxy username-password credentials support for ClientEndpoint using...
Status: NEW
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: WebSocket (show other bugs)
Version: 8.0.x-trunk
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-27 09:15 UTC by Atul Jadhav
Modified: 2017-09-13 11:40 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Atul Jadhav 2016-06-27 09:15:52 UTC
Currently, the websocket ClientEndpoint supports http proxy connection through 'http.proxyHost' and 'http.proxyPort' system properties, but does not support proxy authentication using username-password credentials.

Provide proxy credentials support with parameters passed through 'http.proxyUser' and 'http.proxyPassword' system variables.
Comment 1 Mark Thomas 2016-06-29 14:13:01 UTC
Currently, the WebSocket implmentation uses the standard Proxy API to obtain proxy configuration. 'http.proxyUser' and 'http.proxyPassword' are not part of that API. That is not a blocking issue but it is a concern.
Comment 2 J Fernandez 2017-09-13 02:55:29 UTC
Is this feature still needed? If so, I would like to work on it.
Comment 3 Mark Thomas 2017-09-13 11:40:39 UTC
Yes, there is still interest in adding this feature to Tomcat.

You might find this useful:
https://blogs.oracle.com/wssfc/handling-proxy-server-authentication-requests-in-java

On the basis that system properties are 'recommended' by Oracle - well, used in published examples at least, I'm less concerned.