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 ED1A5200D2E for ; Tue, 31 Oct 2017 11:06:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id EB95B1609EC; Tue, 31 Oct 2017 10:06: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 3DF131609EB for ; Tue, 31 Oct 2017 11:06:04 +0100 (CET) Received: (qmail 91229 invoked by uid 500); 31 Oct 2017 10:06:03 -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 91220 invoked by uid 99); 31 Oct 2017 10:06:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2017 10:06:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B3A6C1A346A for ; Tue, 31 Oct 2017 10:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 9rxPu9WVdPcz for ; Tue, 31 Oct 2017 10:06:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 43AAE60F15 for ; Tue, 31 Oct 2017 10:06:01 +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 8148EE0F1C for ; Tue, 31 Oct 2017 10:06: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 3C6B7212FA for ; Tue, 31 Oct 2017 10:06:00 +0000 (UTC) Date: Tue, 31 Oct 2017 10:06:00 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 10:06:05 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11951: -------------------------------- Fix Version/s: 2.21.0 2.20.1 > 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 > Fix For: 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)