• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Suspect Redirect

Wikibear

Regular Pleskian
I have a redirect with my host from domain.com to anotherdomain.com via created host with 301. Why is that able to get a site from anotherdomain.com/folder/news via domain.com/folder/news?

I think if i set 301 then all request for domain.com will be redirected to anotherdomain.com. My apache server respond on domain.com with links. That looks like an issue for me.
 
When a redirect directive ends with a slash, the redirect is not pointing to the home page of the destination, but is replacing everything before the slash with the domain of the destination. For that reason domain.com/my/test/file redirects to anotherdomain.com/my/test/file and not anotherdomain.com/. This behavior is by design. A redirect destination must not end with a slash to disable this domain replacement.
 
Then i must create a fully host and redirect to the real page? Or is there a better way without creating a fully new host.
 
I see. What you are criticizing is that Plesk always add a trailing slash to the redirect target, which does not enable you to redirect all traffic to the homepage of the target, regardless of the subdirectories a URL can contain.

In that case I suggest to configure the domain as "web space" instead of "forwarding". In the web space create a text file named ".haccess" as the only file in the document root directory. Enter this line into it:
Code:
Redirect 301 / http://anotherdomain.com
 
Back
Top