[Bug 59758] Add http proxy username-password credentials support for ClientEndpoint using system properties

2022-09-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59758

Mark Thomas  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #4 from Mark Thomas  ---


*** This bug has been marked as a duplicate of bug 62312 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 59758] Add http proxy username-password credentials support for ClientEndpoint using system properties

2017-09-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59758

--- Comment #3 from Mark Thomas  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 59758] Add http proxy username-password credentials support for ClientEndpoint using system properties

2017-09-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59758

--- Comment #2 from J Fernandez  ---
Is this feature still needed? If so, I would like to work on it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 59758] Add http proxy username-password credentials support for ClientEndpoint using system properties

2016-06-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59758

--- Comment #1 from Mark Thomas  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org