Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.216.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=S4ygbDRUp4W6XykdYPrm3h6ZoZjg61iV0bDlPO2XHIINBlC4WligUie5ZfsffEyUrp
         MlzGMFg60bGsmPOAY6EB02F+GbdJzIPX5PasX6Yzd1fuejGpxyjpgEUaIaof2b6+K0Oj
         bI9hnK24NdwBYi6OegyG/ApbEV82H8hZoSkVw=
MIME-Version: 1.0
In-Reply-To: <9a01dbec-b8b6-4e36-8542-7b520cf0d0af@email.android.com>
References: <20101208165347.1920E2388A41@eris.apache.org>
	<9a01dbec-b8b6-4e36-8542-7b520cf0d0af@email.android.com>
Date: Wed, 8 Dec 2010 20:16:53 +0000
Message-ID: <AANLkTimZ56b5BFfmFurFAjdndp0P_ze1=mOSS7-j+WA_@mail.gmail.com>
Subject: Re: svn commit: r1043518
From: sebb <sebbaz@gmail.com>
To: HttpComponents Project <dev@hc.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 8 December 2010 20:12, Oleg Kalnichevski <olegk@apache.org> wrote:
> sebb@apache.org wrote:
>
>>Author: sebb
>>Date: Wed Dec =A08 16:53:46 2010
>>New Revision: 1043518
>>
>>URL: http://svn.apache.org/viewvc?rev=3D1043518&view=3Drev
>>Log:
>>Clarify URI content in Execution Context
>>
>>Modified:
>> =A0 =A0httpcomponents/httpclient/trunk/src/docbkx/fundamentals.xml
>> =A0 =A0httpcomponents/httpclient/trunk/src/docbkx/httpagent.xml
>>
>>Modified: httpcomponents/httpclient/trunk/src/docbkx/fundamentals.xml
>>URL:
>>http://svn.apache.org/viewvc/httpcomponents/httpclient/trunk/src/docbkx/f=
undamentals.xml?rev=3D1043518&r1=3D1043517&r2=3D1043518&view=3Ddiff
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>>--- httpcomponents/httpclient/trunk/src/docbkx/fundamentals.xml
>>(original)
>>+++ httpcomponents/httpclient/trunk/src/docbkx/fundamentals.xml Wed Dec
>> 8 16:53:46 2010
>>@@ -543,7 +543,11 @@ byte[] response =3D httpclient.execute(htt
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <formalpara>
>><title><constant>ExecutionContext.HTTP_REQUEST</constant>=3D'http.request=
':</title>
>><para><interfacename>HttpRequest</interfacename> instance representing
>>the
>>- =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0actual HTTP request.</pa=
ra>
>>+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0actual HTTP request.
>>+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0The final HttpRequest ob=
ject in the execution
>>context always represents
>>+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0the state of the message=
 _exactly_ as it was
>>sent to the target server.
>>+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Per default HTTP/1.0 and=
 HTTP/1.1 use relative
>>request URIs.
>>+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</para>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 </formalpara>
>> =A0 =A0 =A0 =A0 =A0 =A0 </listitem>
>> =A0 =A0 =A0 =A0 =A0 =A0 <listitem>
>>
>>Modified: httpcomponents/httpclient/trunk/src/docbkx/httpagent.xml
>>URL:
>>http://svn.apache.org/viewvc/httpcomponents/httpclient/trunk/src/docbkx/h=
ttpagent.xml?rev=3D1043518&r1=3D1043517&r2=3D1043518&view=3Ddiff
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>>--- httpcomponents/httpclient/trunk/src/docbkx/httpagent.xml (original)
>>+++ httpcomponents/httpclient/trunk/src/docbkx/httpagent.xml Wed Dec =A08
>>16:53:46 2010
>>@@ -185,6 +185,9 @@ httpclient.getConnectionManager().shutdo
>>updated depending on the execution context. Therefore the final request
>>properties such
>>as the target host and request URI can be determined by examining the
>>content of the
>> =A0 =A0 =A0 =A0 local HTTP context after the request has been executed.<=
/para>
>>+ =A0 =A0 =A0 =A0<para>The final HttpRequest object in the execution cont=
ext
>>always represents
>>+ =A0 =A0 =A0 =A0 =A0 =A0the state of the message _exactly_ as it was sen=
t to the
>>target server.
>>+ =A0 =A0 =A0 =A0 =A0 =A0Per default HTTP/1.0 and HTTP/1.1 use relative r=
equest
>>URIs.</para>
>> =A0 =A0 =A0 =A0 <programlisting><![CDATA[
>> DefaultHttpClient httpclient =3D new DefaultHttpClient();
>>
>>@@ -197,7 +200,7 @@ HttpUriRequest req =3D (HttpUriRequest) lo
>> =A0 =A0 =A0 =A0 ExecutionContext.HTTP_REQUEST);
>>
>> System.out.println("Target host: " + target);
>>-System.out.println("Final request URI: " + req.getURI());
>>+System.out.println("Final request URI: " + req.getURI()); // relative
>>URI
>
> Sebastian,
>
> The trouble is the uri can also be absolute, if the request has been sent=
 via a proxy without creating a tunnel (direct proxy mode). Basically the u=
ri can either relative or absolute depending on the route.

OK, I'll update the docs.

> Oleg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org