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

Leif Hedstrom updated TS-274:
-----------------------------

    Affects Version/s:     (was: 2.0.1)
                       2.0.0a
        Fix Version/s:     (was: 2.0.1)
                           (was: 2.1.0)
                       2.0.0

> SSL Handshake not work properly
> -------------------------------
>
>                 Key: TS-274
>                 URL: https://issues.apache.org/jira/browse/TS-274
>             Project: Traffic Server
>          Issue Type: Bug
>    Affects Versions: 2.1.0, 2.0.0a
>         Environment: Debian, Linux 2.6.18 32-bit
>            Reporter: Marcus Clyne
>             Fix For: 2.0.0
>
>
> Using self-signed SSL certificates, which are in the correct paths under 
> $prefix, and giving no startup errors, I get the following error when making 
> a request through the proxy :
> Mar 24 14:35:09 www traffic_server[27926]: {1146895248} ERROR: SSL ERROR: 
> SSL_ServerHandShake.
> Mar 24 14:35:09 www traffic_server[27926]: {1146895248} ERROR: 
> SSL::5:error:1407609B:SSL routines:SSL23_GET_CLIENT_HELLO:https proxy 
> request:s23_srvr.c:384:
> Mar 24 14:36:47 www traffic_server[27926]: {1146895248} ERROR: SSL ERROR: 
> SSL_ServerHandShake.
> Mar 24 14:36:47 www traffic_server[27926]: {1146895248} ERROR: 
> SSL::5:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http 
> request:s23_srvr.c:379:
> The first of these two was from using Proxifier (Windows software) to connect 
> to the server, the second is from using `curl -k -x $ip:443 
> http://google.com/`.
> The issue appears on the latest trunk version and the 2.0.x branch as of 
> today when used in forward proxy mode.
> I have not personally tested in reverse proxy mode, but zwoop (Freenode IRC 
> name) tested in reverse proxy mode, and reverse proxy mode worked only in the 
> 2.0.x but not trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to