• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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