Repository navigation
Replies: 2 comments 2 replies
|
The fix has been merged into master and will be included in the next release. |
0 replies
|
@kaplanelad I just tested the branch |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm using loco 0.13.2, currently it always returns 200 even the route not exists. Seems #991 make this, what the right way to return 404 for an unhandled route?
I just tried to enable
fallbackmiddleware, it's not effected.My development.yml:
All reactions