[
https://issues.apache.org/jira/browse/TS-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386893#comment-14386893
]
Zhao Yongming commented on TS-3472:
-----------------------------------
the sniproxy do not need to intercept with ssl server|client, it only take SNI
name and route to the backend. it does not even need to link against with SSL
libary.
with ssl_multicert.config:
dest_ip=* action=tunnel
does not work as we need a ssl cert/key file to act as a SSL intercept?
> 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)
