You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/05/23 21:44:02 UTC

[jira] [Commented] (TS-2677) CONNECT method with remap messes up the scheme

    [ https://issues.apache.org/jira/browse/TS-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007588#comment-14007588 ] 

ASF subversion and git services commented on TS-2677:
-----------------------------------------------------

Commit 33a47714538289570521b66e04c6d6c099b13280 in trafficserver's branch refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=33a4771 ]

TS-2677 Do not apply path / scheme URL changes in remap when method is CONNECT.


> CONNECT method with remap messes up the scheme
> ----------------------------------------------
>
>                 Key: TS-2677
>                 URL: https://issues.apache.org/jira/browse/TS-2677
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 5.0.0
>
>
> If you use CONNECT, yet want to apply remaps, it'll modify the scheme. This seems to mess up various things internally, such that the requests are not properly tunneled. It seems nonsensical to allow medications to the scheme (since the client expects e.g. HTTPS, mapping it to anything else would likely make the client misbehave). This would be the easiest solution, and makes internal states (debug, logging etc.) behave as expected.
> The other option is make the scheme irrelevant to the "core", but not sure what other side effects that might have ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)