• 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.

Issue [Plesk Obsidian] Internal redirects are now public?

P

Patrice Kast

Guest
Hi there,

Since we have updated plesk to obsidian, internal redirects (specified by .htaccess file) are public redirects:

https://example.com/en/home -> https :// example.com/?q=en/home
The browser of the user actually gets redirected by an internal redirect...

Are internal redirects deprecated or is this a bug in plesk or the apache which is used by plesk?

The .htaccess file redirect looks like this:
RewriteEngine on
RewriteCond %{QUERY_STRING} !q=(.*)
RewriteRule (.*) https://%{HTTP_HOST}/index.php?q=$1 [L]

Does anyone know this issue or a solution to this problem? There where no changes to any server settings from our side.

Any help is very appreciated!
 
For us, the website routes doesn't work after the update to Obsedian...

.Htaccess
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ https://%{HTTP_HOST}/index.php [QSA,L]

>>> ERR_TOO_MANY_REDIRECTS
 
Back
Top