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
One of our tests started failing when we upgraded from 1.3.48 to 1.3.52. The test expected that calling a URL with an HTTP method which was not defined for a URL returns status code 405. After the upgrade, status code 404 was returned. I have traced the change in behaviour down to this commit. I also have a minimal example reproducing the problem:
One of our tests started failing when we upgraded from 1.3.48 to 1.3.52. The test expected that calling a URL with an HTTP method which was not defined for a URL returns status code
405
. After the upgrade, status code404
was returned. I have traced the change in behaviour down to this commit. I also have a minimal example reproducing the problem:Expected Behavior
Calling
DELETE /goodbye
should return405
.Note that if I comment out the
delete_hello
method, I start getting405
.Actual Behavior
Calling
DELETE /goodbye
returns404
.Steps to Reproduce the Problem
DELETE /goodbye
from browser or from any other HTTP client.404
status code instead of a405
.Specifications
The text was updated successfully, but these errors were encountered: