Forum Discussion
CirrusHttps is taking 4 seconds on first request while http is lightening fast.
Please help me out
I have one http VS and one https VS (client side profile attached) and I am using the same pool for both.
In client side profile I configured client certificate ignored. Now the problem is that when client dials for the first time it takes upto 4 seconds and 2nd, 3rd requests takes 40ms to 70 ms. While http from the same client takes takes 14ms.
Now I am in trouble that why https is taking so long in first request. There is no problem in the network as I am a network guy.
9 Replies
kunjanNimbostratus
Are you using self-signed/untrusted SSL certificate on the client SSL profile?
Muhammad_Irfan1No I am not using self-signed certificate, its been provided by the Company. But even when I removed the certificate and applied default certificate its still the same delay. As client is not using any certificate and I have configure the client side profile in which I have configured to ask client certificate (ignored). So certificate is not in action.
kunjan_118660Cumulonimbus
Are you using self-signed/untrusted SSL certificate on the client SSL profile?
- Muhammad_Irfan1No I am not using self-signed certificate, its been provided by the Company. But even when I removed the certificate and applied default certificate its still the same delay. As client is not using any certificate and I have configure the client side profile in which I have configured to ask client certificate (ignored). So certificate is not in action.
shaggyyou did not attach the client side profile- kunjan
May be you can do a wireshark on the client machine and see what's happening during and after SSL handshake but before browser do the GET request.
Also, can try the curl from cmd line to see if really slowness is in LTM
curl -w '\nLookup time:\t%{time_namelookup}\nConnect time:\t%{time_connect}\nPreXfer time:\t%{time_pretransfer}\nStartXfer time:\t%{time_starttransfer}\n\nTotal time:\t%{time_total}\n' -o /dev/null -s https://192.168.1.1/- Ed_SummersI might also recommend adding the '-vv' option to curl in Kunjan's suggestion to increase verbosity. It may help indicate if a particular portion of the negotiation/connection is hanging. -Ed
- kunjan_118660
May be you can do a wireshark on the client machine and see what's happening during and after SSL handshake but before browser do the GET request.
Also, can try the curl from cmd line to see if really slowness is in LTM
curl -w '\nLookup time:\t%{time_namelookup}\nConnect time:\t%{time_connect}\nPreXfer time:\t%{time_pretransfer}\nStartXfer time:\t%{time_starttransfer}\n\nTotal time:\t%{time_total}\n' -o /dev/null -s https://192.168.1.1/- Ed_SummersI might also recommend adding the '-vv' option to curl in Kunjan's suggestion to increase verbosity. It may help indicate if a particular portion of the negotiation/connection is hanging. -Ed
