Tag Info

Hot answers tagged

16

The following browsers do support SNI: Internet Explorer 7 of newer, on Windows Vista of newer. Mozilla Firefox 2.0 of later Opera 8.0 or newer (TLS 1.1 protocol needs to be enabled) Opera Mobile with at least version 10.1 b├Ęta on Android Google Chrome (Vista or newer. XP on Chrome 6 or newer) OS X 10.5.7 or newer on Chrome 5.0.342.1 or newer Safari 2.1 of ...


2

Looks like you didnt "escape" the slashes in your directive. Putting backslashes before any / . or : should make it work. Also adding the ^ and $ on the wildcard helps. Heres what we use: Standard Domain: Perhaps there is a consolidated way, but this snippet should work for a standard domain. Change the target of the first rewrite to https if you need all ...


1

HTTP/HTTPS Backlinks Google will treat both backlinks the same since they are protocols and technically the same site, however...! If someone links to your site using HTTP:// and your site is HTTPS only then a redirect action will be required and whenever using a 301 redirect some juice is lost, but its a tiny weenie! amount! and nothing worth worrying ...


1

Try going to the var subfolder in your revive installation. There you can find a file your.domain.here.conf.php. For me things started to work when I set the option requireSSL=1. Oh, and have you checked that your https page only uses banners provided through https? Firefox does not load "acitve mixed content" since Firefox 23 so if you put your banners on ...


1

No, there is no way to get the private key from CSR. It is on purpose, that Sertificate Signing Request (CSR) only contains the public key, because CSR will be sent to a certificate authority for signing, but private keys are supposed to be kept private, i.e. not sent to anyone. If you've lost the key, you'll have to generate a new CSR and keep associated ...


1

Method 1: Install a self signed cert You can give your site a temporary self signed SSL meaning that the site can be accessed via HTTPS and then redirected to HTTP because the site becomes accessible with a self signed, however with a self signed certification peoples browsers are going to first warn about the SSL certification. This warning is unavoidable ...


1

The reason this happends is because of (amongst things) duplicate content. You know that the http and https version are the same page, but Google treats them as two pages, thus duplicate. What you need to do is send a redirect with 301 header. 301 means 'permanent redirect', or simply put: 'dont use this url anymore, use the one I send you to: ...


1

I am not having a deep knowledge of this implementation as i have not performed it yet on any of the client's site, but i think i can help you. So, here you go: You need to make a 301 redirect on all the URLs in .htaccess One thing that need to make sure is the sitemap of the site.You need to change with all the new URLs with HTTPS Make sure that all the ...


1

You need to set up a redirect from http://mywebsite.com/<whatever> to https://mywebsite.com/<whatever>. It's not a DNS issue at all, and how to do it is entirely dependent on exactly what web server software you're using and how it's configured. For example, if you use Apache you can create an .htaccess file in the root directory of your ...



Only top voted, non community-wiki answers of a minimum length are eligible