Facebook
Twitter
J
Jon Nunan
Guest
I've developed a website using Drupal that works fine on my local box.
When a non-logged in user or an unauthorised user tries to access some content they shouldn't be allowed Drupal sends it's own 403 page which seems to be being overwritten by Plesk's 403 page. Drupal's watchdog (basically its log) is logging that it generated the 403 page, but I don't see it as I did on my non-plesk dev box. Instead I see the default Plesk 403 page.
I've tried toggling 'Custom error-docs' but it only seems to alter the look of static html files in a whole other directory. This is not going to work as especially with the 403 page I need to have a dynamic query string with a redirect destination once the user logs in. Am I missing something obvious?
When a non-logged in user or an unauthorised user tries to access some content they shouldn't be allowed Drupal sends it's own 403 page which seems to be being overwritten by Plesk's 403 page. Drupal's watchdog (basically its log) is logging that it generated the 403 page, but I don't see it as I did on my non-plesk dev box. Instead I see the default Plesk 403 page.
I've tried toggling 'Custom error-docs' but it only seems to alter the look of static html files in a whole other directory. This is not going to work as especially with the 403 page I need to have a dynamic query string with a redirect destination once the user logs in. Am I missing something obvious?