Github user SvetlinZarev commented on the issue:
https://github.com/apache/tomcat/pull/39
Hi, I've already created a bugzilla ticket:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60617
> Do you read changelogs?
I do.
---
If your project is set up for it,
Github user SvetlinZarev commented on the issue:
https://github.com/apache/tomcat/pull/39
> Does the CONNECT verb not imply a default port number when none is
present?
@ChristopherSchultz According to [rfc2817 section
5.2](https://www.ietf.org/rfc/rfc2817.txt):
&
Github user SvetlinZarev commented on the issue:
https://github.com/apache/tomcat/pull/39
Issue Description
===
WsWebSocketContainer generates bad CONNECT request when a proxy is used.
The host does not contain port information, hence the app cannot connect to
wss
Github user SvetlinZarev commented on the issue:
https://github.com/apache/tomcat/pull/39
It's not a no-op. Imagine the following case:
WS-Host: wss://echo.websocket.org
proxy-host: proxy
proxy-port: 8080
The flow is as follows:
URI path = the WS
GitHub user SvetlinZarev opened a pull request:
https://github.com/apache/tomcat/pull/39
Provide the correct port when using proxy
Fix "create-connection" failures in case of proxied connection.
The proxy needs the remote port information in order to know
to whi
Github user SvetlinZarev commented on the issue:
https://github.com/apache/tomcat/pull/34
Nope, Boolean.getBoolean("xxx") tries to convert the value of the system
property "xxx" to a boolean or returns false if it's missing. The method name
is indeed very
