[
https://issues.apache.org/jira/browse/CAMEL-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226541#comment-16226541
]
Robert Hillier edited comment on CAMEL-11951 at 10/31/17 10:04 AM:
-------------------------------------------------------------------
Claus,
As described, the "detail" request needs to be handled by one of the proxy
requests, and not a specific request. The proxy works fine, until I add REST
services that contain variable parameters. If you comment out the "detail"
request, you'll find that the requests are proxied successfully. When they are
enabled, proxied requests return 405.
Thanks,
Rob
was (Author: robert.hillier):
Clause,
As described, the "detail" request needs to be handled by one of the proxy
requests, and not a specific request. The proxy works fine, until I add REST
services that contain variable parameters. If you comment out the "detail"
request, you'll find that the requests are proxied successfully. When they are
enabled, proxied requests return 405.
Thanks,
Rob
> Uri matching does not match request type
> ----------------------------------------
>
> Key: CAMEL-11951
> URL: https://issues.apache.org/jira/browse/CAMEL-11951
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common
> Affects Versions: 2.20.0
> Environment: camel-spring, camel-jetty
> OS - RHEL
> Reporter: Robert Hillier
> Attachments: camel-bug-demo.zip
>
>
> I had previously described the problem here:
> https://stackoverflow.com/questions/46936348/apache-camel-rest-dsl-405-method-not-allowed
> It appears that the problem is down to a possible bug in the way URIs are
> matched (not to mention my rather obscure use-case)
> I have a number of REST-DSL endpoints with the same URI but different request
> types (POST, PUT, GET, DELETE). In my case, the URI is getting selected by
> HttpServletResolveConsumerStrategy.resolve (in addition to these, I have some
> specific endpoints with wildcards in them)
> This method matches the URI, but not the request type. When I send a GET
> request, it returns the first consumer candidate it finds which, in my case,
> always seems to be PUT. Later, when CamelContinuationServlet.doService
> checks that the request type and cadidate type match, they don't. It then
> returns 405 Method Not Allowed.
> I believe that the HttpServletResolveConsumerStrategy.resolve method IN
> camel-hhtp-common should check the request type as well as the URI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
