You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "M. Nunberg (JIRA)" <ji...@apache.org> on 2011/08/16 18:32:00 UTC
[jira] [Created] (TS-920) HTTP CONNECT gives bad request line
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-920) HTTP CONNECT gives bad request line
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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.3.0)
> 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
>
> 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
[jira] [Updated] (TS-920) HTTP CONNECT gives bad request line
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ 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.2)
3.1.3
> 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.1.3
>
>
> 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
[jira] [Resolved] (TS-920) HTTP CONNECT gives bad request line
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-920.
------------------------------
Resolution: Duplicate
Marking this as duplicate of TS-1322, which has more details.
> 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
>
> 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
[jira] [Updated] (TS-920) HTTP CONNECT gives bad request line
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ 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.1)
3.1.2
Moving this out to 3.1.2 for now.
> 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.1.2
>
>
> 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
[jira] [Updated] (TS-920) HTTP CONNECT gives bad request line
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ 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: 3.1.1
> 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.1.1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-920) HTTP CONNECT gives bad request line
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ 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