HTTP, HTTPS, Shared SSL, and SEO?

I'm going to guess you'll be okay for number one. If your host does it correctly, individual subdomains never get to see the SSL keys. Here's how it would work.

Up vote 5 down vote favorite share g+ share fb share tw.

I was recently looking around at some of the features my current web host offers, and am now wondering about a few things. Even if you can only answer part of this, I appreciate any help you can provide. I have a domain, mydomian.com, and the host offers shared SSL so I can use HTTPS by using this address myhost.com" rel="nofollow">mydomain.myhost.com.

The SSL certificate is good for *. Myhost.com. I don't know a lot about SSL, but I'm assuming this means that the data between site users and ANY domain on myhost.com is encrypted.

So was curious if this meant that if someone else on the same host as me somehow intercepted the data from my site would they be able to view it, since they would also have a https://theirdomain. Myhost.com address, which uses the same SSL certificate? I may have no idea at all, and this was pretty much a guess.

If HTTPS is used on a login page, but after logging in the other pages are viewed over HTTP, is this a security issue? Is there any way to show a web form via HTTP for bots like Google, but have real users redirected to the HTTPS version? Would be ideal if this could be done via .htaccess.

I currently have some rewrite rules that redirect certain pages to HTTPS, but the rest as HTTP. So if a visitor visits the contact form they get the HTTPS version automatically, but it automatically switches back to HTTP for pages that don't contain forms. So, via htaccess, is there a way to direct real users to the HTTPS version, but have bots directed to the HTTP version?

I would like these pages to still be indexed by the search engines, but would like users to see it via HTTPS. Thanks in advance for any help you can provide. Http ssl https seo link|improve this question edited Oct 6 '11 at 21:26 asked Oct 6 '11 at 20:44Sherwin Flight33910 100% accept rate.

I'm going to guess you'll be okay for number one. If your host does it correctly, individual subdomains never get to see the SSL keys. Here's how it would work: Some guy with a browser sends an encrypted request to your subdomain server.

Your host's master server receives the request and decrypts it. The master server sends the decrypted request to your subdomain server. And any HTTPS responses you send back go through that process in reverse.

It should be easy to check if they've set things up that way: If you can set up shared SSL without personally handling any key files, you're good. If you actually get your hands on some key files... not good. For two: If you encrypt the login, you protect the passwords, which is good.

But if you switch back to HTTP afterwards, you open yourself up to other attacks. See: Firesheep. There may be others.

And for three. Yes - definitely doable. Check out mod_rewrite.

Can't give you an example, as I've never used this particular case, but I can point you to this page - particularly the section entitled "Browser Dependent Content. " Hope that helps!

Every traffic is encrypted, when you use https:// as protocol. (Except for some uncommon circumstances I won't talk about here). An SSL certificate's purpose is to prove the identity of the server, by combining it's public key with an identity.

This certificate is only usable with the private key that belongs to the public one. In your case it seems that this certificate as well as the key-pair is provided by your hosting provider. I guess that neither you nor the other customers on the host have access to this private key.

That means that only your provider is able to decrypt the traffic. Since that's always the case (he's running the server, so has access to every data), that should be no problem. In most cases it is a security issue.

On every further unencrypted http-request the client has to provide some information of the session to the server. These can be intercepted and used by an attacker. (simply speaking) The bots should support https, why not redirect them?

Anyhow: The important part is not to provide the page containing the form via https. To protect your user's data you should take care that the response is transferred via https.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.