Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DAD73107CD for ; Fri, 8 Nov 2013 13:20:31 +0000 (UTC) Received: (qmail 50944 invoked by uid 500); 8 Nov 2013 13:20:29 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 50615 invoked by uid 500); 8 Nov 2013 13:20:22 -0000 Mailing-List: contact dev-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 dev@camel.apache.org Received: (qmail 50607 invoked by uid 99); 8 Nov 2013 13:20:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 13:20:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elakito@gmail.com designates 209.85.220.53 as permitted sender) Received: from [209.85.220.53] (HELO mail-pa0-f53.google.com) (209.85.220.53) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 13:20:15 +0000 Received: by mail-pa0-f53.google.com with SMTP id kx10so2209163pab.12 for ; Fri, 08 Nov 2013 05:19:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=S4NpVrkVCZkru/W1ra3FQaIXVXzF/602zxQUPT997vw=; b=j1mXzPjPPNS5TlkWjnGAb1jC7oRkHqwJ4fCHo8r5bLqVAr2eWKFfsb9VfJLEsqs8gp uCMN+kq4suKwx1QimrkOS4ufDGHab+vi2mvmlfvwBoOv9gVQzAhzvflfL5hq1h/7Wi2R xbuqat1QUQg6dEXXNsTHd+rCvcxNBn01ZSQpMHG0JiMgHW1CrKLqZY4Y37WcWY5RyZTk 9tPp6wxEkHv5yfvMr1eC0t88ZlUCs7qavxSX8GGynugJXYTGtyXs0RkVGj9+xdjZtFeP Xf4k3HZsWSTl2vFK/h66pSQnESksEShk1x3ajUcezdE1NNWB2cWamLDI2G+V9SCMBkDs YQkw== MIME-Version: 1.0 X-Received: by 10.68.137.103 with SMTP id qh7mr14920155pbb.175.1383916793775; Fri, 08 Nov 2013 05:19:53 -0800 (PST) Received: by 10.68.29.71 with HTTP; Fri, 8 Nov 2013 05:19:53 -0800 (PST) In-Reply-To: <8DC4AC1C29B748AA9B578A15451A1217@gmail.com> References: <8DC4AC1C29B748AA9B578A15451A1217@gmail.com> Date: Fri, 8 Nov 2013 14:19:53 +0100 Message-ID: Subject: Re: NettyHttpProducer Request URI From: Aki Yoshida To: dev@camel.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Willem, I agree with you that netty should use the path. but what is the benefit of using the full url? I guess the http 1.1 was changed to allow the full url so that the proxy doesn't need to rewrite the request, could it be? in that case, that will be another argument for the client to be actually using the path instead of the url in this case. regards, aki 2013/11/7 Willem jiang : > Hi team, > > I just found NettyHttpProducer sets the Request URI with the absoluteURI = like > > GET http://www.w3.org/pub/WWW/TheProject.html. > > But I found HttpClient set the Request URI with absolutePath like > > GET /pub/WWW/TheProject.html > Host: www.w3.org > > From the HTTP1.1 RFC[1], these two Request URI are all OK. But for my exp= erience it could be better if NettyHttpProducer can just set the Request UR= I with absolutePath. > In this way, the request can be proxied without changing anything. Such a= s I can use TCPMonitor the check the request and response between the Netty= HttpProducer and back end server without changing anything. > > Any thought? > > [1]http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) = (English) > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: =E5=A7=9C=E5=AE=81willem > > > > >