mstombs
Very Senior Member
Most of it is over my head, but it did seem to increment disconnect data by parsing the text of 'syslog' events. Without proper understanding of https connections though, I can't say whether commenting out some piping would make servstats more 'sensible'? Perhaps my lack of https knowledge is my real problem.
pixelserv can write to syslog, but doesn't parse it. MYLOG is a macro which is null defined in util.h unless compiled with -DVERBOSE
Do clients without a imported Pixelserv root certificates result in a very high cls? ...
good catch, the "cls" will be incremented if the the SSL_accept fails or rv from SSL_read (for https) or recv is zero, the description of "cls" is not necessarily correct, when rv == 0 the client may have cleanly disconnected just not sent any data.
if @kvic is watching we could have more categories of result added, from the ssl section rv==0 could be from default because ssl_err not > 0, OR no data from SSL_read. From the normal connection section both errors rv<0 AND no data rv==0 are lumped together, sorry I probably did that in a much earlier version (before pipes or https!).
Current code starts here https://github.com/kvic-z/pixelserv-tls/blob/master/socket_handler.c#L601
cls counts the number of FAIL_CLOSED pipedata.status returns via the pipe from connection handling process back to main process (.... somehow), SSL status returned via pipedata.ssl .
My current stats from servstats.txt - need to review the certs on my devices!
Code:
pixelserv-tls version: v35.HZ12.Kj compiled: May 31 2017 04:30:23 options: 192.168.66.254 -p 80 -p 81 -p 8080 -p 8081 -k 443 -o 2
2042236 uts, 0 log, 65537 req, 1266 avg, 9097 rmx, 89 tav, 2748 tmx, 60669 slh, 158 slm, 0 sle, 479 slu, 697 nfe, 29 gif, 1 ico, 1190 txt, 0 jpg, 0 png, 0 swf, 3 sta, 1 stt, 73 ufe, 1111 rdr, 0 nou, 0 pth, 0 204, 116 pst, 0 hed, 0 bad, 0 err, 784 tmo, 61532 cls