http:// or https:// loads fast??

I need DP members help...

Can anybody explain which one take more time for loading..

http://www. or https://www.

thanx

 

https because the date is encrypted.

 

are you sure https:// loads fast as compare to http:// ?

 

You asked which one took more time for loading. I said https

 

Thanx for quick reply...

Can you explain why it takes more time?
Any resource link where i can find out the exact reason..?

 

HTTPS is much slower than HTTP!

Because, the https request communicates over SSL involves the process of Encryption and Decryption. The request is first encrypted on the sender’s side and decrypted on the receiver’s side.

Thanks

 

He answered you here. The data has to be encrypted, thats why its slower.

 

http is faster as compared to https

 

HTTP is the standard protocol for clients (Web browsers) and servers (Web servers) to communciate with each other over the Internet. By its very nature, it is unnecrypted, meaning that anyone can intercept and read the data packets that are sent back and forth with a little bit of effort.

HTTPS works differently, since it uses either SSL (Secure Socet Layer) 2 or 3 (or in Opera's case, TLS - which stands for Transport Layer Security - 1.0 or 1.1). When the communication between the client and server is initiated, the server encrypts a "secret key" (in the case of TLS) and sends it to the client (Web browser) so it will be able to "unlock" the encrypted data packets that will follow.

Now don't get me wrong, I'm not an expert on TCP/IP, HTTP, SSL and TSL, or even Web security in general, not by any stretch of the imagination, so I may have gotten part of that wrong. But what it boils down to is HTTPS tends to take longer because it involves the creation of a secure transfer session between the browser and server so that both sides can send encrypted data to each other without fear of being intercepted by someone who wants your visitors' personal data - like credit card numbers, bank account numbers, Social Security Numbers (if in the US), username and password information, and so on.

In the end, don't use HTTPS unless you have to. And if you have a site that requires personal data like usernames, passwords, and credit card numbers, use HTTPS for those parts of the site that need it (such as message board or client login areas), and use standard HTTP for the rest. Also avoid having a login form on each page of your Web site as much as possible, instead using a separate page with an HTTPS connection instead.

 

HTTP: Hyper Text Transfer Protocol - Fast (not encrypted)
HTTPS: Hyper Text Transfer Protocol Secure - Slow (encrypted)

- Robert

 

http:// is faster cause it isnt encrypted

 

I would say https has to be way slower as it is for security reasons, rather than speed.

 

Most browsers are generall set to use the highest encryption standard available, and in many cases will adopt 256-bit encryption which can be slow. If you do not have a business or security need for 256-bit encryption then you can opt for a lower grade encryption.
Like if you are using mozilla :

Try Edit -> Prefernces -> Privacy & Security -> SSL

Click "Edit Ciphers" and go through each of the three tabs and disable anything higher than 128-bit.

 

Thanx Dan Schulz
nice explaination...

 

Thanx guyz for your help...