Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3FC79200D2E for ; Tue, 31 Oct 2017 13:48:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3E408160BF9; Tue, 31 Oct 2017 12:48:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 856021609EB for ; Tue, 31 Oct 2017 13:48:03 +0100 (CET) Received: (qmail 39894 invoked by uid 500); 31 Oct 2017 12:48:02 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 39885 invoked by uid 99); 31 Oct 2017 12:48:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2017 12:48:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E947E18340E for ; Tue, 31 Oct 2017 12:48:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ZrTDyQ7Y5IOJ for ; Tue, 31 Oct 2017 12:48:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E018961103 for ; Tue, 31 Oct 2017 12:48:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 707E4E0662 for ; Tue, 31 Oct 2017 12:48:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 220C0212F7 for ; Tue, 31 Oct 2017 12:48:00 +0000 (UTC) Date: Tue, 31 Oct 2017 12:48:00 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-11951) Uri matching does not match request type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 31 Oct 2017 12:48:04 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226715#comment-16226715 ] Claus Ibsen commented on CAMEL-11951: ------------------------------------- Yes wait for the release > 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 > Assignee: Claus Ibsen > Fix For: 2.19.4, 2.20.1, 2.21.0 > > 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)