Thread: http s
View Single Post
Old 08-12-2004, 01:03 PM   #4 (permalink)
imaginemn
v7n Mentor
 
imaginemn's Avatar
 
Join Date: 02-18-04
Location: Minneapolis, Minnesota
Posts: 1,946
iTrader: 0 / 0%
Latest Blog:
None

imaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to allimaginemn is a name known to all
Send a message via MSN to imaginemn Send a message via Yahoo to imaginemn Send a message via Skype™ to imaginemn
The difference between the two is the encryption and the port they communicate through. HTTP (port 80), HTTPS (port 443). Although it may seem that HTTPS connections are much slower the problem here is that most of the encryption and validation is done on the client side so it takes longer for the request to be received on the server. The HTTPS connections do end up increasing during high volume but it usually takes at least 45 users to be connected to get the same speeds of regular HTTP. So it's safe to say high volume sites do not really see the lower performance. I used to have a few case studies on this topic. I'll try to find them and post them. Very useful information.

Google does index HTTPS sites. If you try allinurl: https you will get the following.

Results 1 - 10 of about 21,300,000 for allinurl: https

In the past they used to have the following statement in their submit guidelines.

Quote:
google only indexes publicly available web pages. Secure sites (https: ) are not included in the google index.
That's no longer on their submission guidelines. But then again they also never included dynamic web sites either.

Hope this helps.

imaginemn
__________________
Need a project done? - Set Your Own Price!
Imagine Creative Services
- Design : Marketing : Multimedia : More
imaginemn is offline   Reply With Quote