All geek questions in one place

WWW vs non WWW - What is the best practice? I need to choose one for my new SSL certificate

Should my site be a www or non-www address? This is a pretty simple question. I wanted to see what people consider best practice here. The reason I should choose is to buy an SSL certificate for one or the other. Of course, I can redirect to the one I choose in the background, and technical problems are not a problem, but are there any opinions on what to choose and why?

+4
source share
4 answers

My vote is for a shorter one. Comparing your question with how to write on the Internet, and write in general - strive for maximum meaning in the least number of words. 4 stored bytes can be useful to third parties such as Twitter.

+3
source

Identification of the answer? Some sellers will offer as standard. I find Go Daddy to offer a service help section below.

http://help.godaddy.com/topic/234/article/850

+7
source

The host name is, in fact, a convenience for your users to remember the name. From this point of view, it is mainly a marketing solution. If you advertised example.com , use this; if you advertised www.example.com , use this.

Back-end redirects, as you seem to suggest, don't sound like a good idea. The certificate point allows the user to verify the identity of your server. If you have only example.com , and if they try www.example.com via HTTPS, they will first receive an invalid certificate warning (so they should not follow the redirect).

You can get both. Some CAs issue SAN certificates for example.com and www.example.com (sometimes at the same price or a little more, I think).

+4
source

SSL certificates support multiple names and also support wildcard pattern matching. I would add 2 names to the certificate; you do not need to choose only one.

Consider adding two site.com and *.site.com to cover you if you need to use an additional host / subdomain in the future.

Please note that both of them are necessary if you want to access the server as site.com , since the name site.com does not match the *.site.com pattern

+1
source

Source: https://habr.com/ru/post/1387273/

More articles:


All Articles