Ticket #2526 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Paths evaluated too broadly

Reported by: miksik@phil.muni.cz Assigned to: Chriki
Priority: normal Component: RestrictedAreaPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10

Description

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

Change History

02/06/08 11:00:50 changed by Chriki

  • status changed from new to closed.
  • resolution set to fixed.

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 :-)

02/06/08 12:07:50 changed by Daniel Miksik <miksik@phil.muni.cz>

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?

Add/Change #2526 (Paths evaluated too broadly)




Change Properties
Action