Skip to content

Request routing should first match on path, then on request method  #24

@ivanr

Description

@ivanr

We currently route requests first based on the request method, then based on path. This leads to a problem when the combination of method and path in the request doesn't match the expected route, most likely leading to a 404. This is confusing if the path is correct, because we should respond with a 405.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions