[
https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533306#comment-13533306
]
Uri Shachar commented on TS-1423:
---------------------------------
@Alan - What would be the point in only bypassing on request line parsing
failure? If the header parsing fails ATS won't be able to handle the request,
and will return an error msg to the user....
> 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_as_port_option.diff,
> 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
