Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
We use 'toboggan/denied' to handle our 403 pages (variable site_403 is set to 'toboggan/denied').
However, 'toboggan/denied' returns a 200 HTTP code and as a result gets indexed by Google, which we don't really want. Shouldn't this page return a 403 instead of a 200 ?
Proposed resolution
Make 'toboggan/denied' return a 403 instead of a 200.
Comments
Comment #2
GuyPaddock CreditAttribution: GuyPaddock at Inveniem commentedI am not able to reproduce this bug. We are using Login Toboggan version 1.5 and it definitely returns a 403 on access denied pages that are using Login Toboggan.