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?

CommentFileSizeAuthor
#3 securesite.module_path.patch2 KBNaX

Comments

NaX’s picture

NaX commented
Assigned: Unassigned » NaX

Looking into it.

PRZ’s picture

PRZ commented

Hi, NaX.

I too would really appreciate an answer to this issue, if you've figured it out.

Thanks!

NaX’s picture

NaX commented
Status: Active » Needs review
StatusFileSize
new securesite.module_path.patch2 KB

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

salvis’s picture

salvis
he/his
commented

This patch works fine for me — thank you!

NaX’s picture

NaX commented
Status: Needs review » Fixed

committed to HEAD, 4.7 and 5

NaX’s picture

NaX commented
Status: Fixed » Closed (fixed)

  • Commit 6443679 on 6.x-2.x, 7.x-2.x, master, 8.x-1.x by NaX: 
    #103289 Protect by url alias