[
https://issues.apache.org/jira/browse/TS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110862#comment-14110862
]
Sudheer Vinukonda commented on TS-2574:
---------------------------------------
Just wanted to emphasize that, the solution committed here is to replace ET_SSL
threads with ET_NET threads when ssl_threads are configured with value "-1",
which will avoid having to share origin sessions across thread pools, when
doing a mixed mode (http to https) connection. The limitation of not being able
to share the origin sessions correctly when using ssl_threads still exists,
but, (as discussed with Leif on the irc), with the plan to eventually phase out
ET_SSL altogether in 6.0 or later, that limitation will not be addressed.
> Sharing server sessions per thread doesn't work when doing https to http
> ------------------------------------------------------------------------
>
> Key: TS-2574
> URL: https://issues.apache.org/jira/browse/TS-2574
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, SSL
> Reporter: Bryan Call
> Assignee: Brian Geffon
> Fix For: 5.1.0
>
> Attachments: TS-2574.patch
>
>
> When running a reverse proxy with incoming https scheme and outgoing http,
> the share server sessions value of 2 doesn't work.
> Since the https and http thread pools are separate after using the http
> connection it will be released to the http thread. When a new https request
> comes in it will look in the https threads servers session pool to make a
> request to the origin even though it is a http request. Of course it will
> fail the lookup since the ports wont match.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
