Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cache flush command fails when no matching page is found #51

Closed
jimlambie opened this issue Apr 11, 2016 · 0 comments
Closed

Cache flush command fails when no matching page is found #51

jimlambie opened this issue Apr 11, 2016 · 0 comments
Assignees
@jimlambie
Labels
status: in progress type: bug
Milestone
1.8.0

Comments

@jimlambie
Copy link
Contributor

The flush command returns a 500 error when there is no matching page found.
jimlambie added a commit that referenced this issue Apr 11, 2016
@jimlambie
fix: use path-to-regex when looking for pages that match the request
3de6c5c 
because Web uses regular expressions to specify page routes, the same
library must be used to test the curret request URL against the loaded
endpoints in order to find a match for the caching module to work with.

Fix #51
@jimlambie jimlambie added this to the 1.4.0 milestone Apr 13, 2016
@jimlambie jimlambie self-assigned this Apr 13, 2016
@jimlambie jimlambie removed this from the 1.4.0 milestone May 25, 2016
@jimlambie jimlambie added this to the 1.8.0 milestone Nov 22, 2016
@abovedave abovedave mentioned this issue Aug 9, 2017
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jimlambie jimlambie

Labels
status: in progress type: bug
Projects
None yet
Milestone
1.8.0
Development

No branches or pull requests
1 participant
@jimlambie