-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
Labels
requestRequest for new functionalityRequest for new functionality
Milestone
Description
Hi.
Consider the following route:
#[post("/hello")]
pub fn hello() -> &'static str {
"Hello"
}now, if you call it with:
curl http://localhost:8000/helloit returns:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>404 Not Found</title>
</head>
<body align="center">
<div align="center">
<h1>404: Not Found</h1>
<p>The requested resource could not be found.</p>
<hr />
<small>Rocket</small>
</div>
</body>
</html>
however, since the passed URL is correct and only the method (verb) is wrong, according to rfc7231#section-6.5.5, it should return 405: Method Not Allowed with an Allow header field in a 405 response containing a list of the target resource's currently supported methods.
So, if you don't agree with that, could you provide a global option to send 405 instead of 404 for handling method not allowed errors?
TIA
awulkan, paolobarbolini, Punie, mateuszkj, mpajkowski and 19 more
Metadata
Metadata
Assignees
Labels
requestRequest for new functionalityRequest for new functionality
Type
Projects
Status
Backlog