[
https://issues.apache.org/jira/browse/TS-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053303#comment-14053303
]
James Peach commented on TS-2802:
---------------------------------
{quote}
1. ./lib/ts/ink_memory.h: #define ats_strndup(p,n) _xstrdup((p), n, NULL).
{quote}
Yup, which is why all code should use {{ats_strndup}}.
{quote}
2. Looks like NetVCOptions includes a few basic protocol & sockets attributes
that are user options and convenient to be assigned, servername seems to be
more reasonable to attach to a client vc, any concerns to alter the interface?
{quote}
No, I don't think that the {{NetVConnection}} interface should be changed for
this. {{NetVCOptions}} is still my preferred solution, though I'm not saying
that you should attach the whole thing to the {{SSLNetVConnection}}. Another
solution could be to add an SSL-extended version of {{connect_re}} to the
{{SSLNetProcessor}} to carry SSL-specific options.
> Add SNI support for origin servers
> ----------------------------------
>
> Key: TS-2802
> URL: https://issues.apache.org/jira/browse/TS-2802
> Project: Traffic Server
> Issue Type: Improvement
> Components: SSL
> Reporter: Bryan Call
> Assignee: Bryan Call
> Labels: Review
> Fix For: 5.1.0
>
> Attachments: TS-2802.diff
>
>
> test to an origin that requires SNI
> {code}
> [bcall@cat ~]$ tail -1 /usr/local/etc/trafficserver/remap.config
> map http://foo.yahoo.com
> https://www.mnot.net/blog/2014/05/09/if_you_can_read_this_youre_sniing
> [bcall@cat ~]$ curl -H 'Host: foo.yahoo.com' http://localhost:8080/; echo
> TLS SNI Required.
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
