Subhash Chopra wrote:
> Outputs from SSLDump with Mozilla and various other browsers(ie IE,Opera
> etc....) revealed the following facts:
>
> In case of a HTTPS request for a web site with say 4 gifs, mozilla opens up 4
> TCP connections and do the SSL handshake including the clientkeyexchange,
> server certificates .... for each one of them.
> While other browsers like IE 5 or opera 5, open up 1 TCP connection and do a
> complete SSL handshake on it... and then these browsers reuse use the session
> id and negotiated values of this first TCP session for the other 3
> connections which are opened for each gif ( for the other 3 TCP connections
> it only performs HELLO and CHANGECIPHERSPEC protocol ).
> This approach adds to performance in terms of the size of bandwidth and time.
When using straight HTTP, does Mozilla do the same thing (i.e. open 4
TCP connections)?
Also, I'm about to roll up my sleeves and dig into the source to see if
I can understand what happens with SSL through a proxy using the CONNECT
method (tunneling proxy). Can someone point me at the area of the code
that handles this?
