[
https://issues.apache.org/jira/browse/CAMEL-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080930#comment-14080930
]
Raúl Kripalani commented on CAMEL-7650:
---------------------------------------
In the fix applied in commit 563d143, how do we differentiate between the
method not being allowed (405) and the resource not existing (404)?
In other words, if we have a Restlet consumer listening on
{{restlet:http://0.0.0.0/abcd?method=POST}}, these two circumstances are
different:
* GET /abcd => should lead to HTTP 405.
* POST /abcd/def => should lead to HTTP 404.
Moreover, RFC2616 specifies the following:
{quote}
10.4.6 405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource
identified by the Request-URI. The response MUST include an Allow header
containing a list of valid methods for the requested resource.
{quote}
So we must return the Allow header along with the HTTP 405.
Can we delegate this stuff to the Restlet engine instead of handling it
manually?
> camel-restlet - Return 405 if method not allowed instead of 404
> ---------------------------------------------------------------
>
> Key: CAMEL-7650
> URL: https://issues.apache.org/jira/browse/CAMEL-7650
> Project: Camel
> Issue Type: Bug
> Components: camel-restlet
> Affects Versions: 2.13.2
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.12.5, 2.13.3, 2.14.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Camel-Restlet-2-13-1-Consumer-Questions-tp5754698.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)