You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 fallback middleware, it's not effected.
My development.yml:
server:
# Port on which the server will listen. the server binding is 0.0.0.0:{PORT}port: 5150# The UI hostname or IP address that mailers will point to.host: http://localhost# Out of the box middleware configuration. to disable middleware you can changed the `enable` field to `false` of comment the middleware blockmiddlewares:
fallback:
enable: truecode: 404static:
enable: truemust_exist: trueprecompressed: falsefolder:
uri: "/"path: "frontend/dist"fallback: "frontend/dist/index.html"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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
fallback
middleware, it's not effected.My development.yml:
Beta Was this translation helpful? Give feedback.
All reactions