Https and WWW

[Walter Smith]

Hello,

I would suggest two main features and very useful features:
-Being able to force HTTPS on domain name.
-Being able to force WWW prefix on domain name.

 

[TobiasP]

To force SSL I would recommend using an .htaccess file.
I don't think there is a way / setting to force it via Plesk.

the www. forcing can also be achieved over .htaccess

Here is an example:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://www.%{HTTP_HOST}%{REQUEST_URI}
</IfModule>

I tried it on my local Webserver (wamp) and it seemed to work.

 

[Alexey.Plotnitsky]

Hi Walter Smith,

Thanks for your suggestions!
1) Agree with forced WWW prefix.
2) Why do you need forced SSL connection?

 

[Sergey L]

Also why forced www-prefix would be required? Why you don't want site accessed as simply domain.com?

Regards

 

[Walter Smith]

Why force SSL Connection:
In order to make sure users only browse our domain using SSL connection. as this is by far better security wise.
Just like how facebook force SSL and Gmail force SSL.
Why force WWW Prefix:
This helps in SEO and on Google+ and facebook likes and search engines. If you already have most links with WWW prefix, it would be better to make that a "standard".

And these can always be turned Off/On using Plesk Panel if implemented.

 

[Amin Taheri]

I know this doesn't contribute much to the thread, and I apologize for that; In my opinion asking if the WWW should be enabled or not is outdated. It should always be enabled and not allowed to be turned off. It doesn't have to be used if they don't want to but it should always be on.