https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
--- Comment #7 from radhika.j...@veritas.com ---
Hi Mark, Any update on this?
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-ma
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
--- Comment #6 from radhika.j...@veritas.com ---
I followed:
https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/samples/sockets/client/SSLSocketClientWithTunneling.java
for Proxy tunneling
--
You are receiving this mail b
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
--- Comment #5 from radhika.j...@veritas.com ---
=
if (proxyConnect != null) {
fConnect.get(timeout, TimeUnit.MILLISECONDS);
// Proxy CONNECT is secure text
if(securePr
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
--- Comment #4 from radhika.j...@veritas.com ---
Hi Mark, Thanks for your response.
Here is some of my understanding and thoughts.
What is the use case for using proxying over TLS vs just using a direct TLS
connection?
>> So some of our Custo
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
--- Comment #3 from Mark Thomas ---
Java's Proxy configuration classes (mainly ProxyType, ProxySelector) don't
support proxies that use TLS between the client and the proxy.
Tomcat's proxy support for WebSocket opted to leverage Java's built-i
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
radhika.j...@veritas.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
Mark Thomas changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=66592
Mark Thomas changed:
What|Removed |Added
Severity|normal |enhancement
--
You are receiving this m
