[
https://issues.apache.org/jira/browse/TS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530031#comment-13530031
]
Alan M. Carroll commented on TS-1423:
-------------------------------------
In general we have been moving toward having multiple listen ports with
different configurations for ease of network administration (e.g., having
transparent and non-transparent ports, SSL and non-SSL), it seems that if we
are configuring whether to do this pass through we should allow it to be
controlled per listening port as well. I see your point about destination
ports, though. I would go ahead and do it because it's not a required feature -
the global configuration would remain and the per port would be used only by
people who really need it.
> 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
