| commit | 85d042d7944cb0a24af1c8563826d3e4d9beb720 | |
| author | rofl0r <retnyg@gmx.net> | |
| Mon, 11 Mar 2013 01:39:49 +0000 (11 02:39 +0100) | ||
| committer | rofl0r <retnyg@gmx.net> | |
| Mon, 11 Mar 2013 01:48:08 +0000 (11 02:48 +0100) | ||
| tree | 8d0d026d0aab51d8b5d74c8f1191d266e24fcb51 | treesnapshot (tar.gz zip) |
| parent | a6f2148ed2853d32a07310fef63819cfbaa9c873 | commitdiff |
remove superfluous autoreconnectonfail and fix SSL reconnect ...
i dont see a point in a separate prefs.autoreconnectonfail
if we already have prefs.autoreconnect.
even worse, the setting was not reachable via gui and could
only be set via /SET.
as for the handler code for this error:
"error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number"
"Are you sure this is a SSL capable server and port?"
the gtk frontend seems to ignore the return value of the function
that handles it (ssl_do_connect()), but in the text frontend
the timeout handler job was removed if the function returned 0.
now, if autoreconnect is set, it will reconnect on this error in
both frontends.
i dont see a point in a separate prefs.autoreconnectonfail
if we already have prefs.autoreconnect.
even worse, the setting was not reachable via gui and could
only be set via /SET.
as for the handler code for this error:
"error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number"
"Are you sure this is a SSL capable server and port?"
the gtk frontend seems to ignore the return value of the function
that handles it (ssl_do_connect()), but in the text frontend
the timeout handler job was removed if the function returned 0.
now, if autoreconnect is set, it will reconnect on this error in
both frontends.
| src/common/cfgfiles.c | diffblobblamehistory | |
| src/common/server.c | diffblobblamehistory |