You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "B Wyatt (JIRA)" <ji...@apache.org> on 2012/08/28 17:39:07 UTC
[jira] [Created] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
B Wyatt created TS-1423:
---------------------------
Summary: Blind tunneling of garbage/invalid requests when using transparent interception
Key: TS-1423
URL: https://issues.apache.org/jira/browse/TS-1423
Project: Traffic Server
Issue Type: New Feature
Affects Versions: 3.2.0
Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
Reporter: B Wyatt
Assignee: Alan M. Carroll
Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
Posted by "Yossi Gottlieb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yossi Gottlieb updated TS-1423:
-------------------------------
Attachment: transparent_passthrough.diff
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
> Attachments: transparent_passthrough.diff
>
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (TS-1423) Blind tunneling of
garbage/invalid requests when using transparent interception
Posted by "Uri Shachar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495144#comment-13495144 ]
Uri Shachar edited comment on TS-1423 at 11/12/12 7:54 AM:
-----------------------------------------------------------
We've got a patch for this that allows the user to configure tunneling if the *first* request fails parsing. Yossi will upload it after a bit of QA.
was (Author: ushachar):
We've got a patch for this that allows the user to configure tunneling if the '''first''' request fails parsing. Yossi will upload it after a bit of QA.
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
Posted by "Uri Shachar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495144#comment-13495144 ]
Uri Shachar commented on TS-1423:
---------------------------------
We've got a patch for this that allows the user to configure tunneling if the '''first''' request fails parsing. Yossi will upload it after a bit of QA.
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1423:
------------------------------
Fix Version/s: 3.3.2
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
Posted by "Yossi Gottlieb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yossi Gottlieb updated TS-1423:
-------------------------------
Attachment: (was: transparent_passthrough.diff)
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
Posted by "Yossi Gottlieb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yossi Gottlieb updated TS-1423:
-------------------------------
Attachment: transparent_passthrough.diff
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
> Attachments: transparent_passthrough.diff
>
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1423) Blind tunneling of garbage/invalid
requests when using transparent interception
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462735#comment-13462735 ]
Alan M. Carroll commented on TS-1423:
-------------------------------------
Looking at this, I don't see an easy way to cache the response. You would need a better cache API so that you could compute a key from the client request which would have to be custom logic in a plugin.
> Blind tunneling of garbage/invalid requests when using transparent interception
> -------------------------------------------------------------------------------
>
> Key: TS-1423
> URL: https://issues.apache.org/jira/browse/TS-1423
> Project: Traffic Server
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Environment: 3.2 with TProxy inteception and proxy.config.http.use_client_target_addr == 1
> Reporter: B Wyatt
> Assignee: Alan M. Carroll
>
> Presently, when ATS encounters a request that it cannot parse or that is malformed in any way, it sends an error response to the client.
> When using transparent interception and proxy.config.http.use_client_target_addr ATS should have enough information to blindly tunnel the original "transmission" to the desired endpoint and maintain the service regardless of HTTP/1.x compliance and moreover if it is non-HTTP communication over port 80.
> Bonus would be support for supporting alien protocols where the server speaks first however, ambiguity over a slow incoming request and an expectation that the server speaks first can make that difficult.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira