• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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