[ https://issues.apache.org/jira/browse/TS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-920: ----------------------------- Fix Version/s: (was: 3.1.5) 3.3.0 Moving this out to 3.3.0, please move back to 3.1.4 if this will be worked on *soon*. Also, take a look at what can be closed here please! > HTTP CONNECT gives bad request line > ----------------------------------- > > Key: TS-920 > URL: https://issues.apache.org/jira/browse/TS-920 > Project: Traffic Server > Issue Type: Bug > Components: HTTP > Reporter: M. Nunberg > Fix For: 3.3.0 > > > An HTTP CONNECT tunnel request such as: > CONNECT foo.com:443 HTTP/1.1 > .... > is translated into: > CONNECT https://foo.com:443/ HTTP/1.1 > .... > and is sent as such to a parent proxy when ATS is configured to forward > requests to parent proxy. This can break the parent proxy in some (all?) > cases, since the semi-standard for CONNECT is a host specification, not a URI. > In practice, for most applications, this issue is quite rare since it is > often pointless to forward CONNECT requests, unless the parent proxy does > some special handling or man-in-the-middle operations etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira