W3C home > Mailing lists > Public > www-lib@w3.org > October to December 2004

Re: Why is HTTPS 10 times slower compared to HTTP

From: Girish S <girishpage@yahoo.com>
Date: Sat, 9 Oct 2004 07:52:21 -0700 (PDT)
Message-ID: <20041009145221.98602.qmail@web52806.mail.yahoo.com>
To: www-lib@w3.org

Hi Daniel,

Thanks for the information,

I have configured Apache server to Keep Connection
alive for 15 seconds.

I see that Libwww in its log prints that says server
closed connection after it receives complete response
for the previous request as below:

Host Event.. host 008A21C0 `x.x.x.x' closed
connection.
 Is this an issue with server or libwww is the
question.

But as you said, if the delay between requests are
kept 0, then I see that the connection is being reused
sometimes. 
Does this mean that Libwww does not support persistant
connection over few ms for HTTPS?

Then moving to libcurl is a better idea?

Girish

--- Daniel Stenberg <daniel@haxx.se> wrote:

> 
> On Sat, 9 Oct 2004, Girish S wrote:
> 
> > I also see that Keep-Alive does not have any
> effect on connection.
> 
> The server limits this. Persistent connections can
> very well be made over 
> HTTPS as well.
> 
> > Libwww and SSL always try to make new connection
> and exchange certs/keys 
> > with the server on every new request made (within
> 2-3 seconds!)
> 
> SSL session id caching drastically reduces
> re-connection times. I don't know 
> of libwww features that. libcurl does.
> 
> -- 
>           -=- Daniel Stenberg -=-
> http://daniel.haxx.se -=-
>    ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo
> un\2\1 is xg'`ol
> 
> 



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Received on Saturday, 9 October 2004 14:52:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:44 GMT