Permissions for SEO-safe 301 redirect from HTTP to HTTPS management
It would be nice for the users to be able to enable or disable:
"Permanent SEO-safe 301 redirect from HTTP to HTTPS"
option in their panel.
Instead of setting it in the service plan, give to the user the permission to manage this feature.
Alvaro Split
shared this idea
Thank you for your input. We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IG
-
Plesk Tech Support
commented
I would like to remove "Permanent SEO-safe 301 redirect from HTTP to HTTPS" from some subscriptions. I still want to keep it as default on a service plan level. I also don't want to customize a subscription since locked subscriptions have caused issues when we want to make changes to service plans. Can you add feature so Service plan has "Permanent SEO-safe 301 redirect from HTTP to HTTPS" as default and it can be turned off by adding Add-on without "Permanent SEO-safe 301 redirect from HTTP to HTTPS"
-
Anonymous
commented
Currently, in Plesk Obsidian, the SSL support management is locked for Customers if the option "Setup of potentially insecure web scripting options that override provider's policy" is disabled. But this option also allows using Perl and Python scripts and unsafe ssh shells.
Since not all new websites are ready for HTTPS out of the box it would be great to make a separate option to lock/unlock SSL support management for Customers without touching scripts and shells.