Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#2526 closed defect (fixed)

Paths evaluated too broadly

Reported by: miksik@… Owned by: Christian Spurk
Priority: normal Component: RestrictedAreaPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10


When adding a path to the restricted paths, it is evaluated too broadly, e.g. adding /wiki/ProjectA will restrict access also to /wiki/ProjectAOverview and so on. Is there any means to make the plugin strict on evaluating paths, if needed?

Attachments (0)

Change History (2)

comment:1 Changed 10 years ago by Christian Spurk

Resolution: fixed
Status: newclosed

Thanks for your bug report! I have fixed the problem with changeset:3184. I'd be glad to hear whether everything works for you now :-)

comment:2 Changed 10 years ago by Daniel Miksik <miksik@…>

Thanks! It works as expected. ;) I wonder though, if there is a simple way of having both the strict and the broad mode built in, and using one of them as needed. Example:

  1. I want to restrict access to all pages beginning with /wiki/ProjectA.
    The path in trac.ini would, read like this: paths=/wiki/ProjectA,/wiki/Whatever.
    If specified this way, the access to /wiki/ProjectBOverview would also be restricted.
  2. I want to restrict access to some pages beginning with /wiki/ProjectB.
    The path in trac.ini would read like this: paths=/wiki/ProjectB/,/wiki/ProjectBInfo/,/wiki/Whatever. If specified this way, the access to /wiki/ProjectBOverview or /wiki/ProjectBInfoUsers would remain unrestricted.

The notation for trac.ini is just an example.

Do you think this is feasible?

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Christian Spurk.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.