[ 
https://issues.apache.org/jira/browse/TS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Geffon updated TS-2574:
-----------------------------

    Comment: was deleted

(was: So disabling ET_SSL threads and fixing this bug is as easy as:

{code}
diff --git a/iocore/net/SSLNetProcessor.cc b/iocore/net/SSLNetProcessor.cc
index eb48672..c15cc46 100644
--- a/iocore/net/SSLNetProcessor.cc
+++ b/iocore/net/SSLNetProcessor.cc
@@ -72,8 +72,9 @@ SSLNetProcessor::start(int number_of_ssl_threads, size_t 
stacksize)
   // Initialize SSL statistics. This depends on an initial set of certificates 
being loaded above.
   SSLInitializeStatistics();
 
-  SSLNetProcessor::ET_SSL = 
eventProcessor.spawn_event_threads(number_of_ssl_threads, "ET_SSL", stacksize);
-  return UnixNetProcessor::start(0, stacksize);
+  //SSLNetProcessor::ET_SSL = 
eventProcessor.spawn_event_threads(number_of_ssl_threads, "ET_SSL", stacksize);
+  //return UnixNetProcessor::start(0, stacksize);
+  return 0;
 }
{code}

I tested and it correctly pulls from the per-thread session pools now. I tested 
both ways HTTPS -> HTTP and HTTP -> HTTPS and everything _seems_ to work...what 
am I missing? I must be missing something?)

> 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
>
>
> 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)

Reply via email to