[
https://issues.apache.org/jira/browse/TS-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387382#comment-14387382
]
Leif Hedstrom commented on TS-3472:
-----------------------------------
This sounds just like a TCP proxy, that uses SNI to identifies the endpoint? I
sort of fail to see why this is a useful feature for ATS, if you have ATS
installed, and you control the traffic to the proxy, and to the origin, why
would you not want to do TLS termination on the proxy layer?
What's a reasonable use case here?
> SNI proxy alike feature for TS
> ------------------------------
>
> Key: TS-3472
> URL: https://issues.apache.org/jira/browse/TS-3472
> Project: Traffic Server
> Issue Type: New Feature
> Components: SSL
> Reporter: Zhao Yongming
> Fix For: sometime
>
>
> when doing forward proxy only setup, the sniproxy:
> https://github.com/dlundquist/sniproxy.git is a very tiny but cool effort to
> setup a TLS layer proxy with SNI, very good for some dirty tasks.
> in ATS, there is already a very good support in all those basic components,
> add SNI blind proxy should be a very good feature, with tiny small changes
> maybe.
> SNI in TLS, will extent the proxy(on caching) into all TLS based services,
> such as mail etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
