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 43CD9200CEC for ; Mon, 21 Aug 2017 10:56:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3F007164B25; Mon, 21 Aug 2017 08:56: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 8300B164B23 for ; Mon, 21 Aug 2017 10:56:03 +0200 (CEST) Received: (qmail 71716 invoked by uid 500); 21 Aug 2017 08:56: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 71707 invoked by uid 99); 21 Aug 2017 08:56: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; Mon, 21 Aug 2017 08:56: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 1DA0B1806E2 for ; Mon, 21 Aug 2017 08:56:02 +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 SAqQGPifRo4K for ; Mon, 21 Aug 2017 08:56: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 1713D5FB0B for ; Mon, 21 Aug 2017 08:56: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 9AD5BE0AF9 for ; Mon, 21 Aug 2017 08:56: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 484A125381 for ; Mon, 21 Aug 2017 08:56:00 +0000 (UTC) Date: Mon, 21 Aug 2017 08:56:00 +0000 (UTC) From: "Andrea Cosentino (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CAMEL-11671) camel-ahc - No way to disable url encoding MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 21 Aug 2017 08:56:04 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-11671: ------------------------------------- Fix Version/s: (was: 2.19.3) > camel-ahc - No way to disable url encoding > ------------------------------------------ > > Key: CAMEL-11671 > URL: https://issues.apache.org/jira/browse/CAMEL-11671 > Project: Camel > Issue Type: Bug > Components: camel-ahc > Affects Versions: 2.19.1 > Reporter: Justin Heesemann > Assignee: Andrea Cosentino > Fix For: 2.20.0 > > > There currently seems to be now way to really disable url encoding for ahc urls with query parameters. > I even tried to use my own ahc binding. > The problem seems to be, that the AhcProducer uses this section: > {code} > public boolean process(Exchange exchange, AsyncCallback callback) { > try { > // AHC supports async processing > Request request = getEndpoint().getBinding().prepareRequest(getEndpoint(), exchange); > log.debug("Executing request {} ", request); > client.prepareRequest(request).execute(new AhcAsyncHandler(exchange, callback, request.getUrl(), getEndpoint().getBufferSize())); > return false; > } catch (Exception e) { > exchange.setException(e); > callback.done(true); > return true; > } > } > {code} > By calling {{client.prepareRequest(request)}} the already created request will be turned again into a request builder with enabled url encoding. > From my perspective this makes no sense: > # we could already return a request builder from the AhcBinding, which would save us some processing time > # the settings on this request builder would then not be overriden > But I can see this would be a breaking change in the API of the AhcBinding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)