• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarding and redirect

T

texken

Guest
For various reasons related to search engine optimization, websites that have multiple urls should apparently have "secondary" urls redirect to the primary url via a 301 permanent redirect rather than simply using the domain alias functionality that Plesk provides.

In performing an experiment I set up a new domain and used the "Standard Forwarding" method and pointed it at my primary url. After allowing for propagation, I ran a server header check on the new secondary url and it returned back a code of 302 rather than 301 (which upon further study is not good for a variety of reasons).

My question is: is there a way within plesk to set 301 redirects or do I need to bypass Plesk and set these up directly in IIS. Or is there a good reason not to do this either. Thanks for any feedback.
 
Can anyone shed light on this isse we have several customer asking of this exact feature?
 
Back
Top