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.
If I define a url alias /protected/test for /node/4 (using the path core module), and I set securesite to bypass every page except for protected/*, then /protected/test is indeed protected, but /node/4 is still accessible to everyone (if the anonymous user has the "access content" permission).
Is there a way to get securesite to check the url alias?
Comment | File | Size | Author |
---|---|---|---|
#3 | securesite.module_path.patch | 2 KB | NaX |
Comments
Comment #1
NaX CreditAttribution: NaX commentedLooking into it.
Comment #2
PRZ CreditAttribution: PRZ commentedHi, NaX.
I too would really appreciate an answer to this issue, if you've figured it out.
Thanks!
Comment #3
NaX CreditAttribution: NaX commentedSorry for the delay.
Please test this patch. This patch should make it so that you can specify pages as normal paths (node/123) or alias paths.
Comment #4
salvisThis patch works fine for me — thank you!
Comment #5
NaX CreditAttribution: NaX commentedcommitted to HEAD, 4.7 and 5
Comment #6
NaX CreditAttribution: NaX commented