Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

Implement regressive matching on url #13

Open
jvoisin opened this issue Nov 30, 2016 · 2 comments
Open

Implement regressive matching on url #13

jvoisin opened this issue Nov 30, 2016 · 2 comments
Assignees
Milestone

Comments

@jvoisin
Copy link

jvoisin commented Nov 30, 2016

It would be great to have regressive matching on url, like:

  • /pif/paf/pouf/test.gif
  • /pif/paf/pouet
  • /pif/pof

would result in a rule on ^/pif/.

@jvoisin jvoisin added this to the 0.1 milestone Nov 30, 2016
@buixor
Copy link
Contributor

buixor commented Nov 30, 2016

Do you mean : ^/pif/[a-z/]+(\.gif)*$?
Generating regex without supervision sounds quite dangerous, as one might abuse the regex, with an url such as /pif/../../../another-file.php

@jvoisin
Copy link
Author

jvoisin commented Nov 30, 2016

.. won't be allowed, yes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants