Geek Answers Handbook

Overview of Configuring HTTPS Connection Settings

I am creating a chat web application that will have to make an AJAX request for every message sent or received. I would like the data to be encrypted, and I tend to run AJAX (with a long poll) over HTTPS.

However, since the request frequency here is much higher than with basic web browsing, I would like to better understand the overhead (network usage, time, server processor, client processor) when setting up an encrypted connection for each HTTPS request.

Besides any general information / advice, I am interested in:

  • As a very rough approximation, how much extra time does an HTTPS request make compared to HTTP? Suppose the content length is 1 byte and the average PC.
  • Will each AJAX request after the first have something significant caching, allowing it to establish a connection faster? If so, how much faster?

Thanks in advance: -)

+1
source share
2 answers

Everything in HTTPS is slower. Personal information cannot be cached, you have encryption at both ends, and SSL handshaking is relatively slow.

A long survey will help. Long airlines are good. Enabling SSL sessions on your server will also avoid significant overhead.

The real trick will do load balancing or any legitimate caching. Not sure how much this will play on your system as a chat server, but this is something to consider.

+1
source

You will receive more detailed information from this article .

( , ,...). . , ( CertificateRequest, , ); , , , .

( , ), , HTTPS, Cache-Control: public.

0

More articles:


All Articles