• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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