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 have noticed that the router isn't compliant with RFC 2616, in that currently it returns a 404 (not found) when a resource is requested with an http method that isn't specified in the application code. I believe this is incorrect, because the resource may actually exist under different methods. Due to the per Method radix tree structure of the router, it would be impossible with the current architecture to implement this compliancy. I have a working solution in my fork for this issue (where all existing unit tests pass), and will reference the pull request with this issue. I would appreciate it if you would take a look.