[stunnel-users] doubts with stunnel.conf

[Gabriel Monnerat]

On 09-08-2011 12:38, Gabriel Monnerat wrote:
> Now I have this in log:
>
> 2011.08.09 11:56:18 LOG5[23690:139807064278800]: Service 
> varnish_SOFTINST-51 accepted connection from 10.0.235.44:58876
> 2011.08.09 11:56:19 LOG5[23690:139807064278800]: connect_blocking: 
> connected 2a01:e34:ec03:8610:*:*:*:*:15000
> 2011.08.09 11:56:19 LOG5[23690:139807064278800]: Service 
> varnish_SOFTINST-51 connected remote server from 
> 2001:0:4137:9e76:0:134:4525:79a7:54770
> 2011.08.09 11:56:19 LOG5[23690:139807064278800]: Connection closed: 56 
> bytes sent to SSL, 460 bytes sent to socket
> 2011.08.09 11:56:29 LOG5[23690:139807064278800]: Service 
> varnish_SOFTINST-51 accepted connection from 10.0.235.44:58888
> 2011.08.09 11:56:29 LOG5[23690:139807064278800]: connect_blocking: 
> connected 2a01:e34:ec03:8610:*:*:*:*:15000
> 2011.08.09 11:56:29 LOG5[23690:139807064278800]: Service 
> varnish_SOFTINST-51 connected remote server from 
> 2001:0:4137:9e76:0:134:4525:79a7:54782
> 2011.08.09 11:56:30 LOG5[23690:139807064278800]: Connection closed: 56 
> bytes sent to SSL, 460 bytes sent to socket
>
> Is this a expected behaviour?
>
> If I try access via browser I have this message...
>
> /Bad Request
>
> Your browser sent a request that this server could not understand /
>
> Because in my case, my architecture is:
>
> Apache > varnish > stunnel > backend
>
> And the varnish have problems to access the stunnel 
This problem was fixed adding this parameters to stunnel.conf:

sslVersion = SSLv3
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1

-- 

Gabriel M. Monnerat