Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2025-01-10 18:50:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

Increase HEADER_MAXSLEEP value to 10

Browse Source 
There is a case where using this on a network with some (slight) instability or slowness can sometimes fail to detect HTTP headers.  Currently, in my testing here, I've seen this range anywhere from 5.7 seconds to 7.8 seconds for a response from getting the headers, so maybe we should consider increasing the time slightly for the header max sleep value.  10 seconds is arbitrary, but still 'short'.

(Feel free to discuss or decline, but I'm hoping we can incorporate this to adapt for slightly slower networks)
This commit is contained in:
Thomas Ward 2016-10-13 13:31:03 -04:00 committed by GitHub
parent d32dbdaff3
commit 3dd081c632
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
testssl.sh
View File

@ -162,7 +162,7 @@ SERVER_SIZE_LIMIT_BUG=false # Some servers have either a ClientHello
# tuning vars, can not be set by a cmd line switch # tuning vars, can not be set by a cmd line switch
EXPERIMENTAL=${EXPERIMENTAL:-false} EXPERIMENTAL=${EXPERIMENTAL:-false}
HEADER_MAXSLEEP=${HEADER_MAXSLEEP:-5} # we wait this long before killing the process to retrieve a service banner / http header HEADER_MAXSLEEP=${HEADER_MAXSLEEP:-10} # we wait this long before killing the process to retrieve a service banner / http header
readonly MAX_WAITSOCK=10 # waiting at max 10 seconds for socket reply readonly MAX_WAITSOCK=10 # waiting at max 10 seconds for socket reply
readonly CCS_MAX_WAITSOCK=5 # for the two CCS payload (each) readonly CCS_MAX_WAITSOCK=5 # for the two CCS payload (each)
readonly HEARTBLEED_MAX_WAITSOCK=8 # for the heartbleed payload readonly HEARTBLEED_MAX_WAITSOCK=8 # for the heartbleed payload