Github user kkolinko commented on the issue:
https://github.com/apache/tomcat/pull/39
OK, thank you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
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, you can
Github user kkolinko commented on the issue:
https://github.com/apache/tomcat/pull/39
Please file this issue into Bugzilla, as documented at
http://tomcat.apache.org/bugreport.html
So that it has proper visibility and can be linked to from a changelog
file. (Do you read
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):
> A
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-HOST
Github user ChristopherSchultz commented on the issue:
https://github.com/apache/tomcat/pull/39
This looks like a no-op change. Does the CONNECT verb not imply a default
port number when none is present?
---
If your project is set up for it, you can reply to this email and have your
