What happens if you remove TIMEOUTclose and accept the default?
Hi,I am using stunnes 4.54, my config looks like this:chroot = /opt/stunnel/jail/setuid = stunnelsetgid = stunnelpid = /stunnel.pidsocket = l:TCP_NODELAY=1socket = r:TCP_NODELAY=1syslog = yesdebug = local1.warningfips = no[http]cert = /opt/stunnel/www.crtkey = /opt/stunnel/www.keysslVersion = alloptions = NO_SSLv2renegotiation = noaccept = 192.168.72.10:443connect = 192.168.71.10:80TIMEOUTclose = 0xforwardedfor = yesMy log is full with:Oct 25 14:49:33 www stunnel: LOG3[15114:140668359968512]: transfer: s_poll_wait: TIMEOUTclose exceeded: closingOct 25 14:49:36 www stunnel: LOG3[15114:140668360591104]: transfer: s_poll_wait: TIMEOUTclose exceeded: closingOct 25 14:50:08 www stunnel: LOG3[15114:140668360812288]: transfer: s_poll_wait: TIMEOUTclose exceeded: closingOct 25 14:50:13 www stunnel: LOG3[15114:140668360591104]: transfer: s_poll_wait: TIMEOUTclose exceeded: closingThe doc suggests to "set to 0 for buggy MSIE" the mailing list tells me "You requested close timeout of 0 seconds and that's exactly what you get."But i still don't understand why this is an error and what can I do to get rid of it? Or is it okay to don't look for errors in the log?Regards,Michael
_______________________________________________
stunnel-users mailing list
stunnel-users@stunnel.org
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users