Nabble - HttpClient-User

HC 4.1 release date

2009-11-13T17:42:58Z

When is HttpClient 4.1 GA release planned?

NullPointerException in AsyncNHttpClientHandler

2009-11-13T11:43:28Z

Oleg,

I am using http nio/core (version 4.0.1) and I got some NullPointerException when the connection times out.

[10002 /127.0.0.1:3556] 2009/11/13 11:29:58.665-0800 DEBUG;[nio.impl.HttpIoReactor:218] Unhandled RuntimeException:
java.lang.NullPointerException
at org.apache.http.nio.protocol.AsyncNHttpClientHandler.timeout(AsyncNHttpClientHandler.java:344)
at org.apache.http.impl.nio.DefaultClientIOEventDispatch.timeout(DefaultClientIOEventDispatch.java:158)
at org.apache.http.impl.nio.reactor.BaseIOReactor.timeoutCheck(BaseIOReactor.java:255)
at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:203)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:260)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:96)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:556)

Looking at the code,

ClientConnState connState = (ClientConnState) context.getAttribute(CONN_STATE);

try {

if (connState.getOutputState() == ClientConnState.EXPECT_CONTINUE) {
......

}catch(IOException e){
}
handleTimeout();

It could happen if the attribute get removed somehow before execution comes here.... It might be safer to check it being NULL or not....

Thanks,
Yong

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: redirection in 4.0

2009-11-13T02:44:14Z

Juanjo wrote:
> Hi folks,
>
> Any ideas about it?
>

I have an idea. How about reading documentation [1] of searching through
the mail archive [2]

[1] http://hc.apache.org/httpcomponents-client/tutorial/html/
[2] http://hc.markmail.org/search/?q=

Oleg

> -----Mensaje original-----
> De: Juanjo [mailto:juanjogoga@...]
> Enviado el: miércoles, 11 de noviembre de 2009 11:08
> Para: 'HttpClient User Discussion'
> Asunto: RE: redirection in 4.0
>
> I don't know what is Web Server 1.0, it is in the response that it isn`t in
> my hands.
>
> How can I do to disable 'expect-continue'?
>
> It work properly on Windows but not on Linux.
>
> I think that the server is a websphere.
>
> -----Mensaje original-----
> De: Oleg Kalnichevski [mailto:olegk@...] Enviado el: miércoles, 11 de
> noviembre de 2009 10:55
> Para: HttpClient User Discussion
> Asunto: RE: redirection in 4.0
>
> On Tue, 2009-11-10 at 18:36 +0100, Juanjo wrote:
>> Hi Oleg, thanks for your answer.
>>
>> These are the diferences
>> Number 2 under windows is running fine.
>> The code is the same in boths environment but in the log, there is a
>> diference in the order that postparams are sent.
>>
>> ¿any ideas?
>>
>> Thanks
>>
>
> For the love of Jesus, what on earth is Web Server 1.0? Whatever that piece
> of software is, it appears to have issues with 'expect-continue'
> handshaking. Interestingly enough, 'expect-continue' appears to work
> properly on Linux and to fail on Windows. So, try disabling
> 'expect-continue' and see if that makes any difference.
>
> Oleg
>
>
>> STACK NUMBER 1- LINUX
>>
>> DEBUG http-8080-17 org.apache.http.impl.client.DefaultRequestDirector
>> - Attempt 1 to execute request DEBUG http-8080-17
>> org.apache.http.impl.conn.DefaultClientConnection - Sending request:
>> POST /posturl HTTP/1.1 DEBUG http-8080-17 org.apache.http.wire - >>
>> "POST /posturl HTTP/1.1[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Content-Length: 474[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Content-Type:
>> application/x-www-form-urlencoded[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Host: www.web.com[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "User-Agent:
>> Apache-HttpClient/4.0 (java 1.5)[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Cookie:
>> JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm;
>> systemKey=www.web.com; DC-Cookie=DC2[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - >> "[EOL]"
>> DEBUG http-8080-17 org.apache.http.headers - >> POST /posturl HTTP/1.1
>> DEBUG http-8080-17 org.apache.http.headers - >> Content-Length: 474
>> DEBUG http-8080-17 org.apache.http.headers - >> Content-Type:
>> application/x-www-form-urlencoded
>> DEBUG http-8080-17 org.apache.http.headers - >> Host: www.web.com
>> DEBUG http-8080-17 org.apache.http.headers - >> Connection: Keep-Alive
>> DEBUG http-8080-17 org.apache.http.headers - >> User-Agent:
>> Apache-HttpClient/4.0 (java 1.5)
>> DEBUG http-8080-17 org.apache.http.headers - >> Expect: 100-Continue
>> DEBUG http-8080-17 org.apache.http.headers - >> Cookie:
>> JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm;
>> systemKey=www.web.com;
>> DC-Cookie=DC2
>> DEBUG http-8080-17 org.apache.http.headers - >> Cookie2: $Version=1
>> DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - << "[EOL]"
>> DEBUG http-8080-17 org.apache.http.impl.conn.DefaultClientConnection -
>> Receiving response: HTTP/1.1 100 Continue DEBUG http-8080-17
>> org.apache.http.headers - << HTTP/1.1 100 Continue DEBUG http-8080-17
>> org.apache.http.wire - >> "...postparams...."
>> DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - << "Date: Tue, 10 Nov 2009
>> 16:59:56 GMT[EOL]"
>> DEBUG http-8080-17 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"
>>
>>
>>
>>
>> STACK NUMBER 2 - WINDOWS
>>
>> DEBUG http-8080-2 org.apache.http.impl.client.DefaultRequestDirector -
>> Attempt 1 to execute request DEBUG http-8080-2
>> org.apache.http.impl.conn.DefaultClientConnection - Sending request:
>> POST /posturl HTTP/1.1 DEBUG http-8080-2 org.apache.http.wire - >>
>> "POST /posturl HTTP/1.1[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Content-Length: 474[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Content-Type:
>> application/x-www-form-urlencoded[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Host: www.web.com[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "User-Agent:
>> Apache-HttpClient/4.0 (java 1.5)[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Cookie:
>> JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n;
>> systemKey=www.web.com; DC-Cookie=DC2[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - >> "[EOL]"
>> DEBUG http-8080-2 org.apache.http.headers - >> POST /postrul HTTP/1.1
>> DEBUG http-8080-2 org.apache.http.headers - >> Content-Length: 474
>> DEBUG http-8080-2 org.apache.http.headers - >> Content-Type:
>> application/x-www-form-urlencoded
>> DEBUG http-8080-2 org.apache.http.headers - >> Host: www.web.com DEBUG
>> http-8080-2 org.apache.http.headers - >> Connection: Keep-Alive DEBUG
>> http-8080-2 org.apache.http.headers - >> User-Agent:
>> Apache-HttpClient/4.0 (java 1.5)
>> DEBUG http-8080-2 org.apache.http.headers - >> Expect: 100-Continue
>> DEBUG http-8080-2 org.apache.http.headers - >> Cookie:
>> JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n;
>> systemKey=www.web.com;
>> DC-Cookie=DC2
>> DEBUG http-8080-2 org.apache.http.headers - >> Cookie2: $Version=1
>> DEBUG http-8080-2 org.apache.http.wire - >> "...postparams..."
>> DEBUG http-8080-2 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - << "[EOL]"
>> DEBUG http-8080-2 org.apache.http.impl.conn.DefaultClientConnection -
>> Receiving response: HTTP/1.1 100 Continue DEBUG http-8080-2
>> org.apache.http.headers - << HTTP/1.1 100 Continue DEBUG http-8080-2
>> org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - << "Date: Tue, 10 Nov 2009
>> 16:51:53 GMT[EOL]"
>> DEBUG http-8080-2 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"
>>
>> -----Mensaje original-----
>> De: Oleg Kalnichevski [mailto:olegk@...] Enviado el: martes, 10
>> de noviembre de 2009 14:08
>> Para: HttpClient User Discussion
>> Asunto: RE: redirection in 4.0
>>
>> On Tue, 2009-11-10 at 12:13 +0100, Juanjo wrote:
>>> The environment was updated to:
>>>
>>> Linux 2.6.18
>>> JDK 1.6.0_16-b01
>>> Tomcat 6.0.20
>>>
>>> and the programs doesn't run.
>>> The same error.
>>>
>>> Juanjo
>>>
>>>
>> Use context / wire logging to examine the HTTP session and find out
>> why your application behaves differently in different environments.
>>
>> http://hc.apache.org/httpcomponents-client/logging.html
>>
>> Oleg
>>
>>
>>>
>>>
>>>
>>> Hi,
>>>
>>> In windows using tomcat 6.0 and jdk 1.6, my program runs properly.
>>> It connect to a website by post, sending parameters, that return a
>>> 302. Then, It reads the Location head an makes a Get call.
>>>
>>> When I deploy this program in linux with tomcat 5, the location
>>> head returns the home url, not the right one.
>>>
>>> This is the code:
>>>
>>> HttpClient client = new DefaultHttpClient();
>>> HttpPost req = new HttpPost(http://www.theweb.com);
>>> List<NameValuePair> formparams = new ArrayList<NameValuePair>();
>>> formparams.add(new BasicNameValuePair("aaa","sss"));
>>> ...
>>> UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
>>> req.setEntity(param)
>>> HttpResponse res = client.execute(req)
>>> entity =res.getEntity();
>>> Header loc = res.getFirstHeader("Location");
>>>
>>> ....
>>>
>>>
>>> Another program that do the same but no redirection and using
>>> BasicResponseHandler runs properly in both systems.
>>>
>>>
>>> Please help,
>>>
>>> Tanks
>>>
>>> Juanjo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
>> For additional commands, e-mail: httpclient-users-help@...
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
>> For additional commands, e-mail: httpclient-users-help@...
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: jakartacommons-httpclient-3.x: 3 seconds additional latency in response times

2009-11-13T02:42:31Z

Amit M Bhosle wrote:

> Hi:
>
> occasionally, the response sent by my server arrives at my client after a
> delay of 3 seconds! the delay occurs only occasionally (e.g., 1 in few 100
> or so requests is impacted).
>
> I've verified that there's no delay in setting up the connection, and the
> request from the client reaching the server, but the response gets delayed
> for whatever reason. someone pointed me to the TCP 3-way handshake which
> includes the SYN retry (which has a default retry after 3 seconds), and the
> TCP handshake is executed both at connection setup and tear-down stages. but
> I'm not sure if the connection tear-down is blocking for the communication.
>
> I'm considering moving to persistent connections for other reasons too, but
> that would not help if the tear-down is non-blocking.
>
> my client uses JakartaCommons-httpclient-3.0.1 , and was wondering if
> there's any known issue with this version.
>
> any insights/pointers would be appreciated.
>
> thanks
> AB
>

I am nor aware of reports of this kind of problem by other users.
Regardless, you should consider upgrading to version 4.0

Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

RE: redirection in 4.0

2009-11-12T23:52:27Z

Hi folks,

Any ideas about it?

-----Mensaje original-----
De: Juanjo [mailto:juanjogoga@...]
Enviado el: miércoles, 11 de noviembre de 2009 11:08
Para: 'HttpClient User Discussion'
Asunto: RE: redirection in 4.0

I don't know what is Web Server 1.0, it is in the response that it isn`t in
my hands.

How can I do to disable 'expect-continue'?

It work properly on Windows but not on Linux.

I think that the server is a websphere.

-----Mensaje original-----
De: Oleg Kalnichevski [mailto:olegk@...] Enviado el: miércoles, 11 de
noviembre de 2009 10:55
Para: HttpClient User Discussion
Asunto: RE: redirection in 4.0

On Tue, 2009-11-10 at 18:36 +0100, Juanjo wrote:

> Hi Oleg, thanks for your answer.
>
> These are the diferences
> Number 2 under windows is running fine.
> The code is the same in boths environment but in the log, there is a
> diference in the order that postparams are sent.
>
> ¿any ideas?
>
> Thanks
>

For the love of Jesus, what on earth is Web Server 1.0? Whatever that piece
of software is, it appears to have issues with 'expect-continue'
handshaking. Interestingly enough, 'expect-continue' appears to work
properly on Linux and to fail on Windows. So, try disabling
'expect-continue' and see if that makes any difference.

Oleg

>
> STACK NUMBER 1- LINUX
>
> DEBUG http-8080-17 org.apache.http.impl.client.DefaultRequestDirector
> - Attempt 1 to execute request DEBUG http-8080-17
> org.apache.http.impl.conn.DefaultClientConnection - Sending request:
> POST /posturl HTTP/1.1 DEBUG http-8080-17 org.apache.http.wire - >>
> "POST /posturl HTTP/1.1[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Content-Length: 474[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Content-Type:
> application/x-www-form-urlencoded[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Host: www.web.com[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "User-Agent:
> Apache-HttpClient/4.0 (java 1.5)[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Cookie:
> JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm;
> systemKey=www.web.com; DC-Cookie=DC2[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "[EOL]"
> DEBUG http-8080-17 org.apache.http.headers - >> POST /posturl HTTP/1.1
> DEBUG http-8080-17 org.apache.http.headers - >> Content-Length: 474
> DEBUG http-8080-17 org.apache.http.headers - >> Content-Type:
> application/x-www-form-urlencoded
> DEBUG http-8080-17 org.apache.http.headers - >> Host: www.web.com
> DEBUG http-8080-17 org.apache.http.headers - >> Connection: Keep-Alive
> DEBUG http-8080-17 org.apache.http.headers - >> User-Agent:
> Apache-HttpClient/4.0 (java 1.5)
> DEBUG http-8080-17 org.apache.http.headers - >> Expect: 100-Continue
> DEBUG http-8080-17 org.apache.http.headers - >> Cookie:
> JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm;
> systemKey=www.web.com;
> DC-Cookie=DC2
> DEBUG http-8080-17 org.apache.http.headers - >> Cookie2: $Version=1
> DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - << "[EOL]"
> DEBUG http-8080-17 org.apache.http.impl.conn.DefaultClientConnection -
> Receiving response: HTTP/1.1 100 Continue DEBUG http-8080-17
> org.apache.http.headers - << HTTP/1.1 100 Continue DEBUG http-8080-17
> org.apache.http.wire - >> "...postparams...."
> DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - << "Date: Tue, 10 Nov 2009
> 16:59:56 GMT[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"
>
>
>
>
> STACK NUMBER 2 - WINDOWS
>
> DEBUG http-8080-2 org.apache.http.impl.client.DefaultRequestDirector -
> Attempt 1 to execute request DEBUG http-8080-2
> org.apache.http.impl.conn.DefaultClientConnection - Sending request:
> POST /posturl HTTP/1.1 DEBUG http-8080-2 org.apache.http.wire - >>
> "POST /posturl HTTP/1.1[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Content-Length: 474[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Content-Type:
> application/x-www-form-urlencoded[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Host: www.web.com[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "User-Agent:
> Apache-HttpClient/4.0 (java 1.5)[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Cookie:
> JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n;
> systemKey=www.web.com; DC-Cookie=DC2[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "[EOL]"
> DEBUG http-8080-2 org.apache.http.headers - >> POST /postrul HTTP/1.1
> DEBUG http-8080-2 org.apache.http.headers - >> Content-Length: 474
> DEBUG http-8080-2 org.apache.http.headers - >> Content-Type:
> application/x-www-form-urlencoded
> DEBUG http-8080-2 org.apache.http.headers - >> Host: www.web.com DEBUG
> http-8080-2 org.apache.http.headers - >> Connection: Keep-Alive DEBUG
> http-8080-2 org.apache.http.headers - >> User-Agent:
> Apache-HttpClient/4.0 (java 1.5)
> DEBUG http-8080-2 org.apache.http.headers - >> Expect: 100-Continue
> DEBUG http-8080-2 org.apache.http.headers - >> Cookie:
> JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n;
> systemKey=www.web.com;
> DC-Cookie=DC2
> DEBUG http-8080-2 org.apache.http.headers - >> Cookie2: $Version=1
> DEBUG http-8080-2 org.apache.http.wire - >> "...postparams..."
> DEBUG http-8080-2 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - << "[EOL]"
> DEBUG http-8080-2 org.apache.http.impl.conn.DefaultClientConnection -
> Receiving response: HTTP/1.1 100 Continue DEBUG http-8080-2
> org.apache.http.headers - << HTTP/1.1 100 Continue DEBUG http-8080-2
> org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - << "Date: Tue, 10 Nov 2009
> 16:51:53 GMT[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"
>
> -----Mensaje original-----
> De: Oleg Kalnichevski [mailto:olegk@...] Enviado el: martes, 10
> de noviembre de 2009 14:08
> Para: HttpClient User Discussion
> Asunto: RE: redirection in 4.0
>
> On Tue, 2009-11-10 at 12:13 +0100, Juanjo wrote:
> > The environment was updated to:
> >
> > Linux 2.6.18
> > JDK 1.6.0_16-b01
> > Tomcat 6.0.20
> >
> > and the programs doesn't run.
> > The same error.
> >
> > Juanjo
> >
> >
>
> Use context / wire logging to examine the HTTP session and find out
> why your application behaves differently in different environments.
>
> http://hc.apache.org/httpcomponents-client/logging.html
>
> Oleg
>
>
> >
> >
> >
> >
> > Hi,
> >
> > In windows using tomcat 6.0 and jdk 1.6, my program runs properly.
> > It connect to a website by post, sending parameters, that return a
> > 302. Then, It reads the Location head an makes a Get call.
> >
> > When I deploy this program in linux with tomcat 5, the location
> > head returns the home url, not the right one.
> >
> > This is the code:
> >
> > HttpClient client = new DefaultHttpClient();
> > HttpPost req = new HttpPost(http://www.theweb.com);
> > List<NameValuePair> formparams = new ArrayList<NameValuePair>();
> > formparams.add(new BasicNameValuePair("aaa","sss"));
> > ...
> > UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
> > req.setEntity(param)
> > HttpResponse res = client.execute(req)
> > entity =res.getEntity();
> > Header loc = res.getFirstHeader("Location");
> >
> > ....
> >
> >
> > Another program that do the same but no redirection and using
> > BasicResponseHandler runs properly in both systems.
> >
> >
> > Please help,
> >
> > Tanks
> >
> > Juanjo
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

jakartacommons-httpclient-3.x: 3 seconds additional latency in response times

2009-11-12T18:42:12Z

Hi:

occasionally, the response sent by my server arrives at my client after a
delay of 3 seconds! the delay occurs only occasionally (e.g., 1 in few 100
or so requests is impacted).

I've verified that there's no delay in setting up the connection, and the
request from the client reaching the server, but the response gets delayed
for whatever reason. someone pointed me to the TCP 3-way handshake which
includes the SYN retry (which has a default retry after 3 seconds), and the
TCP handshake is executed both at connection setup and tear-down stages. but
I'm not sure if the connection tear-down is blocking for the communication.

I'm considering moving to persistent connections for other reasons too, but
that would not help if the tear-down is non-blocking.

my client uses JakartaCommons-httpclient-3.0.1 , and was wondering if
there's any known issue with this version.

any insights/pointers would be appreciated.

thanks
AB

Re: MultipartEntity and HttpMultipart

2009-11-12T13:24:07Z

Hi Oleg,

Yes, that answers my question, thanks.

Scott.

Oleg Kalnichevski wrote:

> On Thu, 2009-11-12 at 15:47 +1100, Scott Yeadon wrote:
>
>> Hi,
>>
>> Using HTTP components 4.0 I wanted to create a POST request using the
>> multipart/mixed content type. However the MultipartEntity does not allow
>> the contentType to be set and is hardcoded to multipart/form-data.
>> Looking through the API it looks as though the HttpMultipart class (and
>> its associated classes) are available to address the various multipart
>> media types, however it appears to be incompatible with HttpPost addPart
>> method as HttpMultipart does not implement the HttpEntity interface. I
>> could not locate an obvious class used for request handling for
>> "HttpMultipart"-based requests. It appears the simplest means to POST a
>> request with multipart/mixed contentType is to create a new entity class
>> implementing HttpEntity (e.g. MultipartMixedEntity) - is that correct or
>> are there other means of doing this with the 4.0 API?
>>
>>
>
> You will be better off just overriding the #generateContentTypre method
> of the MultipartEntity class.
>
>
>
>> Also, what is the relation between these sets of entity classes - the
>> HttpEntity implentations appear in the "entity" package and the others
>> appear in the "mime" package? Is there some sort of de-lineation or
>> usage rules for these classes I should be aware of?
>>
>>
>
> HttpMime is somewhat special because it is not fully API stable due to
> its dependency on Mime4j, which is still considered API unstable.
>
> Hope this answers your question.
>
> Oleg
>
>
>> Thanks.
>>
>> Scott.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
>> For additional commands, e-mail: httpclient-users-help@...
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Poor performance of pooled connections worse in 4.0

2009-11-12T11:27:00Z

Hi Tony.

Oleg was right to question my initial benchmark. In the connection pool
benchmark, I was only issuing one request per thread, and contrary to my
intuition, each thread runs slowly at first, even if other threads have
already run the same code (i.e. it has already been JIT compiled).
Subsequent requests in each thread were much faster. It didn't take anywhere
near 10,000 requests to reach stable, optimal performance, though. The
second and third requests in each thread, for example, were just as fast as
the rest.

You might be wondering if the slowness of the first request that I'm talking
about can be attributed to establishing an HTTP connection that is then
reused by subsequent requests. Nope. I saw the same effect even when using a
new HttpClient per request (i.e. no connection pooling or reuse).

Initially, my observations on one of our production servers rose two
questions in my mind:
1) Is the overhead for pooling and reusing connections greater than the
overhead of establishing new HTTP connections?
2) Is the performance of pooled connections significantly worse in
HttpClient 4.0 than in 3.1?

After improving my benchmarks, I've concluded that, in general, the answer
to both questions is "no" (as one would expect). Reusing connections
increases throughput a bit when there's a steady stream of requests that
need to be made to a particular host, and 4.0's
ThreadSafeClientConnManager performs
roughly as well as 3.1's MultiThreadedHttpConnectionManager. Our server that
was having problems was both low on memory and occasionally CPU bound. I
believe it was those conditions that made 4.0's ThreadSafeClientConnManager
slow for us when we first switched to it in production.

I'm still not certain which configuration minimizes request latency when
requests need to made to a single host pretty often, but at random times. I
hope to have the time to answer this question for our use case by
experimentation in the coming week.

Regards,
Jared

On Thu, Nov 12, 2009 at 5:38 AM, Tony Poppleton
<tony.poppleton@...>wrote:

> Hi Jared,
>
> I would be very interested to know if you have made any further progress on
> this potential problem.
>
> Thanks,
> Tony
>
> Jared Jacobs wrote:
>
>> Thanks again for your response, Oleg.
>>
>> We're dealing with a latency problem. The total duration of each and every
>> request needs to be reliably small. Throughput isn't very important in our
>> application.
>>
>> I'll get to the bottom of the issue with some profiling.
>>
>> Cheers,
>> Jared
>>
>>
>> ---------------------------------------------------------------------------------------
>> Orange vous informe que cet e-mail a ete controle par l'anti-virus mail.
>> Aucun virus connu a ce jour par nos services n'a ete detecte.
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>

Re: httpclient and mulitthreaded connection manager

2009-11-12T10:47:42Z

monmohan wrote:
> thanks for the response.
> I have observed that whenever the number of simultaneous threads is close to
> the max limit, the threads go to infinite waiting state. Is this a known
> issue?

HttpClient 3.x is not known to have such an issue. Most likely your
application code leaks connections by failing to release them back to
the pool.

Oleg

I am running on Ubuntu Linux, sun jdk 1.5, http client 3.0.1

>
> regards
> Monmohan
>
>
> olegk wrote:
>> On Wed, 2009-11-11 at 18:36 -0800, monmohan wrote:
>>> I need to implement a scenario where a http request is sent to the same
>>> host
>>> by multiple threads and requires login but the login credentials are
>>> always
>>> same. In order to avoid logging in all the time I am planning to use a
>>> single instance of HTTPClient with a multithreaded connection manager.
>>> However, while testing I ran into scenarios where different threads were
>>> waiting infinitely for a connection. This seems to happen when the number
>>> of
>>> threads is close to the maximum number of connections set up for the
>>> connection manager. In general what is the connection pooling strategy
>>> for
>>> this connection manager? Does the pool grow in size as the number of
>>> simultaneous requests are greater than the configured pool size?
>> No, it does not. The connection pool will not grow beyond the max limit.
>> This is the whole point of having a max limit in the first place.
>>
>> Oleg
>>
>>
>>> Is there an
>>> alternate way to achieve what I am trying to do?
>>> regards
>>> Monmohan
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
>> For additional commands, e-mail: httpclient-users-help@...
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Poor performance of pooled connections worse in 4.0

2009-11-12T05:38:50Z

Hi Jared,

I would be very interested to know if you have made any further progress
on this potential problem.

Thanks,
Tony

Jared Jacobs wrote:

> Thanks again for your response, Oleg.
>
> We're dealing with a latency problem. The total duration of each and every
> request needs to be reliably small. Throughput isn't very important in our
> application.
>
> I'll get to the bottom of the issue with some profiling.
>
> Cheers,
> Jared
>
> ---------------------------------------------------------------------------------------
> Orange vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: httpclient and mulitthreaded connection manager

2009-11-12T05:25:55Z

thanks for the response.
I have observed that whenever the number of simultaneous threads is close to the max limit, the threads go to infinite waiting state. Is this a known issue? I am running on Ubuntu Linux, sun jdk 1.5, http client 3.0.1

regards
Monmohan

olegk wrote:

On Wed, 2009-11-11 at 18:36 -0800, monmohan wrote:
> I need to implement a scenario where a http request is sent to the same host
> by multiple threads and requires login but the login credentials are always
> same. In order to avoid logging in all the time I am planning to use a
> single instance of HTTPClient with a multithreaded connection manager.
> However, while testing I ran into scenarios where different threads were
> waiting infinitely for a connection. This seems to happen when the number of
> threads is close to the maximum number of connections set up for the
> connection manager. In general what is the connection pooling strategy for
> this connection manager? Does the pool grow in size as the number of
> simultaneous requests are greater than the configured pool size?

No, it does not. The connection pool will not grow beyond the max limit.
This is the whole point of having a max limit in the first place.

Oleg

> Is there an
> alternate way to achieve what I am trying to do?
> regards
> Monmohan

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

RE: bidirectional communication based on HttpDefaultClient

2009-11-12T04:47:35Z

On Thu, 2009-11-12 at 09:55 +0100, Simeon Mitev wrote:

> Hi Oleg,
>
> When I use a common socket communication I can get InputStream and
> OutputStream from the connection. Then I am able to read and write as many
> times I need without closing the connection at all.
>
> The same I need to do over http and have it done many times but without
> using httpclient component up to now.
>
> Let say the scenario is as follows:
>
> 1. there are 2 applications (A and B)
> 2. A posts data (HTTP POST) to B
> 3. B posts back to A the data received (2) plus providing an authentication
> key
> 4. A compares what has been initially sent (2) against what has been
> recently received from B (3)
> 5. A responses back to B with OK or FALSE
> 6. A checks whether the status for the last post (5) is HTTP 200 OK (the
> request has been properly received from B)
>
> I can do this only using socket connection but then I need to deal with all
> HTTP protocol's stuffs. Therefore I want to use org.apache.httpcomponents in
> order to facilitate the work. The whole communication described must be done
> without session tracing and using the same connection initially established
> by application A. Finally, A is responsible to close it.
>

That would be a direct violation, or at the very least bastardization,
of the HTTP protocol. HttpClient cannot be used to support such a
scenario and I doubt any of the existing HTTP clients could.

If you are absolutely sure you need to pervert HTTP in this way your
only option seems to be using HttpCore low level classes.

Oleg

> @Simeon
>
>
>
> -----Original Message-----
> From: Oleg Kalnichevski [mailto:olegk@...]
> Sent: Mittwoch, 11. November 2009 20:55
> To: HttpClient User Discussion
> Subject: Re: bidirectional communication based on HttpDefaultClient
>
> Simeon Mitev wrote:
> >
> >
> > Hi guys,
> >
> >
> >
> > I am pretty new to the mailing list and I already have a question :-)
> >
> >
> >
> > If you are familiar with PayPal instant payment notifications (IPN) you
> > probably know the mechanism:
> >
> >
> >
> > 1. PayPal server sends (http post) a notification to provide by the
> > customer URL.
> > 2. The receiver is obligated to send back received data and provide
> > a secured key in addition.
> > 3. PayPal server validates and confirms whether the data has been
> > really sent by him and whether the data is properly parsed by the
> > receiver.
> >
> >
> >
> > I need to implement the same kind of proof of receive via http and the
> > question is how can I do this using
> >
> > HttpDefaultClient, HttpPost and ResponseHandler ?
> >
> >
> >
> > Is it possible once to open communication channels (read and write) and
> > then reuse them until the communication between both sides completes?
> >
> >
>
> I am not entirely sure I understand the question. Of course, HttpClient
> supports bidirectional communication as required by the HTTP spec.
> However, HTTP protocol is based on the concept of request / response
> exchanges. The client must issue a request in order to get a response
> from the server, or, in other words, HTTP client is always an initiator
> of a request / response exchange.
>
> For details on HttpClient programming see:
>
> http://hc.apache.org/httpcomponents-client/tutorial/html/
>
> Hope this helps
>
> Oleg
>
>
> > Thanks
> >
> > @Simeon
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: MultipartEntity and HttpMultipart

2009-11-12T04:38:22Z

On Thu, 2009-11-12 at 15:47 +1100, Scott Yeadon wrote:

> Hi,
>
> Using HTTP components 4.0 I wanted to create a POST request using the
> multipart/mixed content type. However the MultipartEntity does not allow
> the contentType to be set and is hardcoded to multipart/form-data.
> Looking through the API it looks as though the HttpMultipart class (and
> its associated classes) are available to address the various multipart
> media types, however it appears to be incompatible with HttpPost addPart
> method as HttpMultipart does not implement the HttpEntity interface. I
> could not locate an obvious class used for request handling for
> "HttpMultipart"-based requests. It appears the simplest means to POST a
> request with multipart/mixed contentType is to create a new entity class
> implementing HttpEntity (e.g. MultipartMixedEntity) - is that correct or
> are there other means of doing this with the 4.0 API?
>

You will be better off just overriding the #generateContentTypre method
of the MultipartEntity class.

> Also, what is the relation between these sets of entity classes - the
> HttpEntity implentations appear in the "entity" package and the others
> appear in the "mime" package? Is there some sort of de-lineation or
> usage rules for these classes I should be aware of?
>

HttpMime is somewhat special because it is not fully API stable due to
its dependency on Mime4j, which is still considered API unstable.

Hope this answers your question.

Oleg

> Thanks.
>
> Scott.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: httpclient and mulitthreaded connection manager

2009-11-12T04:32:04Z

On Wed, 2009-11-11 at 18:36 -0800, monmohan wrote:

> I need to implement a scenario where a http request is sent to the same host
> by multiple threads and requires login but the login credentials are always
> same. In order to avoid logging in all the time I am planning to use a
> single instance of HTTPClient with a multithreaded connection manager.
> However, while testing I ran into scenarios where different threads were
> waiting infinitely for a connection. This seems to happen when the number of
> threads is close to the maximum number of connections set up for the
> connection manager. In general what is the connection pooling strategy for
> this connection manager? Does the pool grow in size as the number of
> simultaneous requests are greater than the configured pool size?

No, it does not. The connection pool will not grow beyond the max limit.
This is the whole point of having a max limit in the first place.

Oleg

> Is there an
> alternate way to achieve what I am trying to do?
> regards
> Monmohan

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

RE: bidirectional communication based on HttpDefaultClient

2009-11-12T00:55:01Z

Hi Oleg,

When I use a common socket communication I can get InputStream and
OutputStream from the connection. Then I am able to read and write as many
times I need without closing the connection at all.

The same I need to do over http and have it done many times but without
using httpclient component up to now.

Let say the scenario is as follows:

1. there are 2 applications (A and B)
2. A posts data (HTTP POST) to B
3. B posts back to A the data received (2) plus providing an authentication
key
4. A compares what has been initially sent (2) against what has been
recently received from B (3)
5. A responses back to B with OK or FALSE
6. A checks whether the status for the last post (5) is HTTP 200 OK (the
request has been properly received from B)

I can do this only using socket connection but then I need to deal with all
HTTP protocol's stuffs. Therefore I want to use org.apache.httpcomponents in
order to facilitate the work. The whole communication described must be done
without session tracing and using the same connection initially established
by application A. Finally, A is responsible to close it.

@Simeon

-----Original Message-----
From: Oleg Kalnichevski [mailto:olegk@...]
Sent: Mittwoch, 11. November 2009 20:55
To: HttpClient User Discussion
Subject: Re: bidirectional communication based on HttpDefaultClient

Simeon Mitev wrote:

>
>
> Hi guys,
>
>
>
> I am pretty new to the mailing list and I already have a question :-)
>
>
>
> If you are familiar with PayPal instant payment notifications (IPN) you
> probably know the mechanism:
>
>
>
> 1. PayPal server sends (http post) a notification to provide by the
> customer URL.
> 2. The receiver is obligated to send back received data and provide
> a secured key in addition.
> 3. PayPal server validates and confirms whether the data has been
> really sent by him and whether the data is properly parsed by the
> receiver.
>
>
>
> I need to implement the same kind of proof of receive via http and the
> question is how can I do this using
>
> HttpDefaultClient, HttpPost and ResponseHandler ?
>
>
>
> Is it possible once to open communication channels (read and write) and
> then reuse them until the communication between both sides completes?
>
>

I am not entirely sure I understand the question. Of course, HttpClient
supports bidirectional communication as required by the HTTP spec.
However, HTTP protocol is based on the concept of request / response
exchanges. The client must issue a request in order to get a response
from the server, or, in other words, HTTP client is always an initiator
of a request / response exchange.

For details on HttpClient programming see:

http://hc.apache.org/httpcomponents-client/tutorial/html/

Hope this helps

Oleg

> Thanks
>
> @Simeon
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Get Server Certificates using HttpClient via Proxy connection

2009-11-12T00:00:19Z

Thanks for the plug, Oleg!

To get server certs through a proxy:

java -jar not-yet-commons-ssl-0.3.11.jar

That should print out usage note. Look for " -r --proxy "
command-line switches.

Not-yet-commons-ssl knows nothing about NTLM, but probably the server
will give out its certificate before the NTLM happens.

I feel extremely anal / pedantic for mentioning this, but hey, any
involvement with SSL or security demands it: you are vulnerable to a
man-in-the-middle giving out a fake certificate in this moment. It's
better to get certificates you intend to trust "out-of-band", or at
least verify their signatures out-of-band (e.g. over a telephone line
talking to server admin from the other side directly).

yours,

Julius

On Tue, Nov 10, 2009 at 5:05 AM, Oleg Kalnichevski <olegk@...> wrote:

> On Tue, 2009-11-10 at 00:51 -0800, DUset wrote:
>> Anyone could you help me to get server certificates using HttpClient using
>> proxy connection.(I need to use NTLM authentication Scheme for Proxy
>> aunthentication ).
>
> HttpClient cannot be used to retrieve SSL certificates. I recommend
> using this utility for that:
>
> http://juliusdavies.ca/commons-ssl/
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>

--
yours,

Julius Davies
250-592-2284 (Home)
250-893-4579 (Mobile)
http://juliusdavies.ca/logging.html

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

MultipartEntity and HttpMultipart

2009-11-11T20:47:58Z

Hi,

Using HTTP components 4.0 I wanted to create a POST request using the
multipart/mixed content type. However the MultipartEntity does not allow
the contentType to be set and is hardcoded to multipart/form-data.
Looking through the API it looks as though the HttpMultipart class (and
its associated classes) are available to address the various multipart
media types, however it appears to be incompatible with HttpPost addPart
method as HttpMultipart does not implement the HttpEntity interface. I
could not locate an obvious class used for request handling for
"HttpMultipart"-based requests. It appears the simplest means to POST a
request with multipart/mixed contentType is to create a new entity class
implementing HttpEntity (e.g. MultipartMixedEntity) - is that correct or
are there other means of doing this with the 4.0 API?

Also, what is the relation between these sets of entity classes - the
HttpEntity implentations appear in the "entity" package and the others
appear in the "mime" package? Is there some sort of de-lineation or
usage rules for these classes I should be aware of?

Thanks.

Scott.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

httpclient and mulitthreaded connection manager

2009-11-11T18:36:18Z

I need to implement a scenario where a http request is sent to the same host by multiple threads and requires login but the login credentials are always same. In order to avoid logging in all the time I am planning to use a single instance of HTTPClient with a multithreaded connection manager. However, while testing I ran into scenarios where different threads were waiting infinitely for a connection. This seems to happen when the number of threads is close to the maximum number of connections set up for the connection manager. In general what is the connection pooling strategy for this connection manager? Does the pool grow in size as the number of simultaneous requests are greater than the configured pool size? Is there an alternate way to achieve what I am trying to do?
regards
Monmohan

Re: bidirectional communication based on HttpDefaultClient

2009-11-11T11:54:45Z

Simeon Mitev wrote:

bidirectional communication based on HttpDefaultClient

2009-11-11T04:29:47Z

Hi guys,

I am pretty new to the mailing list and I already have a question :-)

If you are familiar with PayPal instant payment notifications (IPN) you
probably know the mechanism:

1. PayPal server sends (http post) a notification to provide by the
customer URL.
2. The receiver is obligated to send back received data and provide
a secured key in addition.
3. PayPal server validates and confirms whether the data has been
really sent by him and whether the data is properly parsed by the
receiver.

I need to implement the same kind of proof of receive via http and the
question is how can I do this using

HttpDefaultClient, HttpPost and ResponseHandler ?

Is it possible once to open communication channels (read and write) and
then reuse them until the communication between both sides completes?

Thanks

@Simeon

RE: redirection in 4.0

2009-11-11T02:07:38Z

I don't know what is Web Server 1.0, it is in the response that it isn`t in
my hands.

How can I do to disable 'expect-continue'?

It work properly on Windows but not on Linux.

I think that the server is a websphere.

-----Mensaje original-----
De: Oleg Kalnichevski [mailto:olegk@...]
Enviado el: miércoles, 11 de noviembre de 2009 10:55
Para: HttpClient User Discussion
Asunto: RE: redirection in 4.0

On Tue, 2009-11-10 at 18:36 +0100, Juanjo wrote:

RE: redirection in 4.0

2009-11-11T01:54:34Z

On Tue, 2009-11-10 at 18:36 +0100, Juanjo wrote:

For the love of Jesus, what on earth is Web Server 1.0? Whatever that
piece of software is, it appears to have issues with 'expect-continue'
handshaking. Interestingly enough, 'expect-continue' appears to work
properly on Linux and to fail on Windows. So, try disabling
'expect-continue' and see if that makes any difference.

Oleg

>
> STACK NUMBER 1- LINUX
>
> DEBUG http-8080-17 org.apache.http.impl.client.DefaultRequestDirector -
> Attempt 1 to execute request
> DEBUG http-8080-17 org.apache.http.impl.conn.DefaultClientConnection -
> Sending request: POST /posturl HTTP/1.1
> DEBUG http-8080-17 org.apache.http.wire - >> "POST /posturl HTTP/1.1[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Content-Length: 474[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Content-Type:
> application/x-www-form-urlencoded[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Host: www.web.com[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "User-Agent:
> Apache-HttpClient/4.0 (java 1.5)[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Cookie:
> JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm; systemKey=www.web.com;
> DC-Cookie=DC2[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - >> "[EOL]"
> DEBUG http-8080-17 org.apache.http.headers - >> POST /posturl HTTP/1.1
> DEBUG http-8080-17 org.apache.http.headers - >> Content-Length: 474
> DEBUG http-8080-17 org.apache.http.headers - >> Content-Type:
> application/x-www-form-urlencoded
> DEBUG http-8080-17 org.apache.http.headers - >> Host: www.web.com
> DEBUG http-8080-17 org.apache.http.headers - >> Connection: Keep-Alive
> DEBUG http-8080-17 org.apache.http.headers - >> User-Agent:
> Apache-HttpClient/4.0 (java 1.5)
> DEBUG http-8080-17 org.apache.http.headers - >> Expect: 100-Continue
> DEBUG http-8080-17 org.apache.http.headers - >> Cookie:
> JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm; systemKey=www.web.com;
> DC-Cookie=DC2
> DEBUG http-8080-17 org.apache.http.headers - >> Cookie2: $Version=1
> DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - << "[EOL]"
> DEBUG http-8080-17 org.apache.http.impl.conn.DefaultClientConnection -
> Receiving response: HTTP/1.1 100 Continue
> DEBUG http-8080-17 org.apache.http.headers - << HTTP/1.1 100 Continue
> DEBUG http-8080-17 org.apache.http.wire - >> "...postparams...."
> DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - << "Date: Tue, 10 Nov 2009
> 16:59:56 GMT[EOL]"
> DEBUG http-8080-17 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"
>
>
>
>
> STACK NUMBER 2 - WINDOWS
>
> DEBUG http-8080-2 org.apache.http.impl.client.DefaultRequestDirector -
> Attempt 1 to execute request
> DEBUG http-8080-2 org.apache.http.impl.conn.DefaultClientConnection -
> Sending request: POST /posturl HTTP/1.1
> DEBUG http-8080-2 org.apache.http.wire - >> "POST /posturl HTTP/1.1[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Content-Length: 474[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Content-Type:
> application/x-www-form-urlencoded[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Host: www.web.com[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "User-Agent:
> Apache-HttpClient/4.0 (java 1.5)[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Cookie:
> JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n; systemKey=www.web.com;
> DC-Cookie=DC2[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - >> "[EOL]"
> DEBUG http-8080-2 org.apache.http.headers - >> POST /postrul HTTP/1.1
> DEBUG http-8080-2 org.apache.http.headers - >> Content-Length: 474
> DEBUG http-8080-2 org.apache.http.headers - >> Content-Type:
> application/x-www-form-urlencoded
> DEBUG http-8080-2 org.apache.http.headers - >> Host: www.web.com
> DEBUG http-8080-2 org.apache.http.headers - >> Connection: Keep-Alive
> DEBUG http-8080-2 org.apache.http.headers - >> User-Agent:
> Apache-HttpClient/4.0 (java 1.5)
> DEBUG http-8080-2 org.apache.http.headers - >> Expect: 100-Continue
> DEBUG http-8080-2 org.apache.http.headers - >> Cookie:
> JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n; systemKey=www.web.com;
> DC-Cookie=DC2
> DEBUG http-8080-2 org.apache.http.headers - >> Cookie2: $Version=1
> DEBUG http-8080-2 org.apache.http.wire - >> "...postparams..."
> DEBUG http-8080-2 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - << "[EOL]"
> DEBUG http-8080-2 org.apache.http.impl.conn.DefaultClientConnection -
> Receiving response: HTTP/1.1 100 Continue
> DEBUG http-8080-2 org.apache.http.headers - << HTTP/1.1 100 Continue
> DEBUG http-8080-2 org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - << "Date: Tue, 10 Nov 2009 16:51:53
> GMT[EOL]"
> DEBUG http-8080-2 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"
>
> -----Mensaje original-----
> De: Oleg Kalnichevski [mailto:olegk@...]
> Enviado el: martes, 10 de noviembre de 2009 14:08
> Para: HttpClient User Discussion
> Asunto: RE: redirection in 4.0
>
> On Tue, 2009-11-10 at 12:13 +0100, Juanjo wrote:
> > The environment was updated to:
> >
> > Linux 2.6.18
> > JDK 1.6.0_16-b01
> > Tomcat 6.0.20
> >
> > and the programs doesn't run.
> > The same error.
> >
> > Juanjo
> >
> >
>
> Use context / wire logging to examine the HTTP session and find out why your
> application behaves differently in different environments.
>
> http://hc.apache.org/httpcomponents-client/logging.html
>
> Oleg
>
>
> >
> >
> >
> >
> > Hi,
> >
> > In windows using tomcat 6.0 and jdk 1.6, my program runs properly.
> > It connect to a website by post, sending parameters, that return a
> > 302. Then, It reads the Location head an makes a Get call.
> >
> > When I deploy this program in linux with tomcat 5, the location
> > head returns the home url, not the right one.
> >
> > This is the code:
> >
> > HttpClient client = new DefaultHttpClient();
> > HttpPost req = new HttpPost(http://www.theweb.com);
> > List<NameValuePair> formparams = new ArrayList<NameValuePair>();
> > formparams.add(new BasicNameValuePair("aaa","sss"));
> > ...
> > UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
> > req.setEntity(param)
> > HttpResponse res = client.execute(req)
> > entity =res.getEntity();
> > Header loc = res.getFirstHeader("Location");
> >
> > ....
> >
> >
> > Another program that do the same but no redirection and using
> > BasicResponseHandler runs properly in both systems.
> >
> >
> > Please help,
> >
> > Tanks
> >
> > Juanjo
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

RE: redirection in 4.0

2009-11-10T09:36:20Z

Hi Oleg, thanks for your answer.

These are the diferences
Number 2 under windows is running fine.
The code is the same in boths environment but in the log, there is a
diference in the order that postparams are sent.

¿any ideas?

Thanks

STACK NUMBER 1- LINUX

DEBUG http-8080-17 org.apache.http.impl.client.DefaultRequestDirector -
Attempt 1 to execute request
DEBUG http-8080-17 org.apache.http.impl.conn.DefaultClientConnection -
Sending request: POST /posturl HTTP/1.1
DEBUG http-8080-17 org.apache.http.wire - >> "POST /posturl HTTP/1.1[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Content-Length: 474[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Content-Type:
application/x-www-form-urlencoded[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Host: www.web.com[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "User-Agent:
Apache-HttpClient/4.0 (java 1.5)[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Cookie:
JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm; systemKey=www.web.com;
DC-Cookie=DC2[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
DEBUG http-8080-17 org.apache.http.wire - >> "[EOL]"
DEBUG http-8080-17 org.apache.http.headers - >> POST /posturl HTTP/1.1
DEBUG http-8080-17 org.apache.http.headers - >> Content-Length: 474
DEBUG http-8080-17 org.apache.http.headers - >> Content-Type:
application/x-www-form-urlencoded
DEBUG http-8080-17 org.apache.http.headers - >> Host: www.web.com
DEBUG http-8080-17 org.apache.http.headers - >> Connection: Keep-Alive
DEBUG http-8080-17 org.apache.http.headers - >> User-Agent:
Apache-HttpClient/4.0 (java 1.5)
DEBUG http-8080-17 org.apache.http.headers - >> Expect: 100-Continue
DEBUG http-8080-17 org.apache.http.headers - >> Cookie:
JSESSIONID=0001G-b2dgLkoDiImRI5ktlH-RV:12kcoiifm; systemKey=www.web.com;
DC-Cookie=DC2
DEBUG http-8080-17 org.apache.http.headers - >> Cookie2: $Version=1
DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
DEBUG http-8080-17 org.apache.http.wire - << "[EOL]"
DEBUG http-8080-17 org.apache.http.impl.conn.DefaultClientConnection -
Receiving response: HTTP/1.1 100 Continue
DEBUG http-8080-17 org.apache.http.headers - << HTTP/1.1 100 Continue
DEBUG http-8080-17 org.apache.http.wire - >> "...postparams...."
DEBUG http-8080-17 org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
DEBUG http-8080-17 org.apache.http.wire - << "Date: Tue, 10 Nov 2009
16:59:56 GMT[EOL]"
DEBUG http-8080-17 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"

STACK NUMBER 2 - WINDOWS

DEBUG http-8080-2 org.apache.http.impl.client.DefaultRequestDirector -
Attempt 1 to execute request
DEBUG http-8080-2 org.apache.http.impl.conn.DefaultClientConnection -
Sending request: POST /posturl HTTP/1.1
DEBUG http-8080-2 org.apache.http.wire - >> "POST /posturl HTTP/1.1[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Content-Length: 474[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Content-Type:
application/x-www-form-urlencoded[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Host: www.web.com[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Connection: Keep-Alive[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "User-Agent:
Apache-HttpClient/4.0 (java 1.5)[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Expect: 100-Continue[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Cookie:
JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n; systemKey=www.web.com;
DC-Cookie=DC2[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "Cookie2: $Version=1[EOL]"
DEBUG http-8080-2 org.apache.http.wire - >> "[EOL]"
DEBUG http-8080-2 org.apache.http.headers - >> POST /postrul HTTP/1.1
DEBUG http-8080-2 org.apache.http.headers - >> Content-Length: 474
DEBUG http-8080-2 org.apache.http.headers - >> Content-Type:
application/x-www-form-urlencoded
DEBUG http-8080-2 org.apache.http.headers - >> Host: www.web.com
DEBUG http-8080-2 org.apache.http.headers - >> Connection: Keep-Alive
DEBUG http-8080-2 org.apache.http.headers - >> User-Agent:
Apache-HttpClient/4.0 (java 1.5)
DEBUG http-8080-2 org.apache.http.headers - >> Expect: 100-Continue
DEBUG http-8080-2 org.apache.http.headers - >> Cookie:
JSESSIONID=0001509uExGX_9cx6bxRHps1kpj:12vigpo4n; systemKey=www.web.com;
DC-Cookie=DC2
DEBUG http-8080-2 org.apache.http.headers - >> Cookie2: $Version=1
DEBUG http-8080-2 org.apache.http.wire - >> "...postparams..."
DEBUG http-8080-2 org.apache.http.wire - << "HTTP/1.1 100 Continue[EOL]"
DEBUG http-8080-2 org.apache.http.wire - << "[EOL]"
DEBUG http-8080-2 org.apache.http.impl.conn.DefaultClientConnection -
Receiving response: HTTP/1.1 100 Continue
DEBUG http-8080-2 org.apache.http.headers - << HTTP/1.1 100 Continue
DEBUG http-8080-2 org.apache.http.wire - << "HTTP/1.1 302 Found[EOL]"
DEBUG http-8080-2 org.apache.http.wire - << "Date: Tue, 10 Nov 2009 16:51:53
GMT[EOL]"
DEBUG http-8080-2 org.apache.http.wire - << "Server: Web Server 1.0[EOL]"

-----Mensaje original-----
De: Oleg Kalnichevski [mailto:olegk@...]
Enviado el: martes, 10 de noviembre de 2009 14:08
Para: HttpClient User Discussion
Asunto: RE: redirection in 4.0

On Tue, 2009-11-10 at 12:13 +0100, Juanjo wrote:

> The environment was updated to:
>
> Linux 2.6.18
> JDK 1.6.0_16-b01
> Tomcat 6.0.20
>
> and the programs doesn't run.
> The same error.
>
> Juanjo
>
>

Use context / wire logging to examine the HTTP session and find out why your
application behaves differently in different environments.

http://hc.apache.org/httpcomponents-client/logging.html

Oleg

>
>
>
>
> Hi,
>
> In windows using tomcat 6.0 and jdk 1.6, my program runs properly.
> It connect to a website by post, sending parameters, that return a
> 302. Then, It reads the Location head an makes a Get call.
>
> When I deploy this program in linux with tomcat 5, the location
> head returns the home url, not the right one.
>
> This is the code:
>
> HttpClient client = new DefaultHttpClient();
> HttpPost req = new HttpPost(http://www.theweb.com);
> List<NameValuePair> formparams = new ArrayList<NameValuePair>();
> formparams.add(new BasicNameValuePair("aaa","sss"));
> ...
> UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
> req.setEntity(param)
> HttpResponse res = client.execute(req)
> entity =res.getEntity();
> Header loc = res.getFirstHeader("Location");
>
> ....
>
>
> Another program that do the same but no redirection and using
> BasicResponseHandler runs properly in both systems.
>
>
> Please help,
>
> Tanks
>
> Juanjo

RE: redirection in 4.0

2009-11-10T05:07:46Z

On Tue, 2009-11-10 at 12:13 +0100, Juanjo wrote:

> The environment was updated to:
>
> Linux 2.6.18
> JDK 1.6.0_16-b01
> Tomcat 6.0.20
>
> and the programs doesn't run.
> The same error.
>
> Juanjo
>
>

Use context / wire logging to examine the HTTP session and find out why
your application behaves differently in different environments.

http://hc.apache.org/httpcomponents-client/logging.html

Oleg

>
>
>
>
> Hi,
>
> In windows using tomcat 6.0 and jdk 1.6, my program runs properly. It
> connect to a website by post, sending parameters, that return a 302. Then,
> It reads the Location head an makes a Get call.
>
> When I deploy this program in linux with tomcat 5, the location head
> returns the home url, not the right one.
>
> This is the code:
>
> HttpClient client = new DefaultHttpClient();
> HttpPost req = new HttpPost(http://www.theweb.com);
> List<NameValuePair> formparams = new ArrayList<NameValuePair>();
> formparams.add(new BasicNameValuePair("aaa","sss"));
> ...
> UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
> req.setEntity(param)
> HttpResponse res = client.execute(req)
> entity =res.getEntity();
> Header loc = res.getFirstHeader("Location");
>
> ....
>
>
> Another program that do the same but no redirection and using
> BasicResponseHandler runs properly in both systems.
>
>
> Please help,
>
> Tanks
>
> Juanjo

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Get Server Certificates using HttpClient via Proxy connection

2009-11-10T05:05:03Z

On Tue, 2009-11-10 at 00:51 -0800, DUset wrote:
> Anyone could you help me to get server certificates using HttpClient using
> proxy connection.(I need to use NTLM authentication Scheme for Proxy
> aunthentication ).

HttpClient cannot be used to retrieve SSL certificates. I recommend
using this utility for that:

http://juliusdavies.ca/commons-ssl/

Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

RE: redirection in 4.0

2009-11-10T03:13:16Z

The environment was updated to:

Linux 2.6.18
JDK 1.6.0_16-b01
Tomcat 6.0.20

and the programs doesn't run.
The same error.

Juanjo

Hi,

In windows using tomcat 6.0 and jdk 1.6, my program runs properly. It
connect to a website by post, sending parameters, that return a 302. Then,
It reads the Location head an makes a Get call.

When I deploy this program in linux with tomcat 5, the location head
returns the home url, not the right one.

This is the code:

HttpClient client = new DefaultHttpClient();
HttpPost req = new HttpPost(http://www.theweb.com);
List<NameValuePair> formparams = new ArrayList<NameValuePair>();
formparams.add(new BasicNameValuePair("aaa","sss"));
...
UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
req.setEntity(param)
HttpResponse res = client.execute(req)
entity =res.getEntity();
Header loc = res.getFirstHeader("Location");

....

Another program that do the same but no redirection and using
BasicResponseHandler runs properly in both systems.

Please help,

Tanks

Juanjo

Get Server Certificates using HttpClient via Proxy connection

2009-11-10T00:51:47Z

Anyone could you help me to get server certificates using HttpClient using proxy connection.(I need to use NTLM authentication Scheme for Proxy aunthentication ).

redirection in 4.0

2009-11-09T23:48:03Z

Hi,

In windows using tomcat 6.0 and jdk 1.6, my program runs properly. It
connect to a website by post, sending parameters, that return a 302. Then,
It reads the Location head an makes a Get call.

When I deploy this program in linux with tomcat 5, the location head
returns the home url, not the right one.

This is the code:

HttpClient client = new DefaultHttpClient();
HttpPost req = new HttpPost(http://www.theweb.com);
List<NameValuePair> formparams = new ArrayList<NameValuePair>();
formparams.add(new BasicNameValuePair("aaa","sss"));
...
UrlEncodedFormEntity param = new UrlEncodedFormEntity(formparams);
req.setEntity(param)
HttpResponse res = client.execute(req)
entity =res.getEntity();
Header loc = res.getFirstHeader("Location");

....

Another program that do the same but no redirection and using
BasicResponseHandler runs properly in both systems.

Please help,

Tanks

Juanjo

RE: Sending SOAP request using HTTPPost (HttpClient 4.0)

2009-11-09T22:26:01Z

The best way to do this would be to try and simulate the steps using
HttpClient in the same way as a browser does.

If you have Mozilla Firefox, use the HttpFox plugin and see the sequence
of GET and POST request and responses when you interact with your web
server using the browser. Then try to follow the same/similar sequence
of GET and POSTs using the HttpClient and it should work.

I had a similar problem, where after the authentication (login) to the
server, there was an implicit POST from the browser using a javascript
code which happened without the user having to POST anything explicitly.
When I was trying to login using the HttpClient and then trying to do a
GET on something else, it was failing. Then I did a similar POST (the
implicit POST done by javascript) using HttpClient after the login POST
and then I was able to proceed successfully.

So, the problem is not necessarily with the HttpClient. It could be how
your server likes to be interacted with....find that out and do the same
using HttpClient and I am sure it will work. I have been using
HttpClient to perform quite complicated series of POSTs, GETs and
Redirects in my project....and it's been working fine and as expected.
But I have had to find the proper sequence by observing the browser
behavior first.

Hope this helps...

Thanks,
Brijesh

-----Original Message-----
From: Oleg Kalnichevski [mailto:olegk@...]
Sent: Tuesday, November 10, 2009 3:10 AM
To: HttpClient User Discussion
Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)

arpita dhundia wrote:
> I tried setting the expect 100 continue param false but the problem
still persists..
>
> I am performimg very simple stpes, using NTLm authentication, creating
an HTTPPost object and attaching a StringEntity object to it, on which I
have written the xml data.
> Wireshark shows that the post data is not in the right format, hence
the recieving server sends back an HTTP 400 error.
> I am not sure what I am doing wrong, or maybe what can I do to avoid
this error.
>

Doe not use Wireshark. Use wire log of HttpClient instead

http://hc.apache.org/httpcomponents-client/logging.html

Oleg

http://hc.apache.org/httpcomponents-client/tutorial/pdf/httpclient-tutor
ial.pdf
>
> best regards,
> Thierry Boileau
>
>> Thanks for the reply Oleg, could you guide a little how can I do
that?

>>
>> Regards,
>> Arpita
>>
>> --- On Sat, 31/10/09, Oleg Kalnichevski <olegk@...> wrote:
>>
>> From: Oleg Kalnichevski <olegk@...>
>> Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)
>> To: "HttpClient User Discussion" <httpclient-users@...>
>> Date: Saturday, 31 October, 2009, 4:40 AM
>>
>> arpita dhundia wrote:
>>> Hello Folks,
>>>
>>> I have run into a very odd problem.
>>> I have to send a SOAP (xml data over HTTP Post) request to another

server behind NTLM authentication. I am using HttpClient 4.0 for that.
>>> The NTLM authentication works fine but when I try to send the xml
data using StringEntity and set that Entity to the HTTPPpost Object, I
am returned 400 error code, meaning "bad request".
>>> I tried to see the exact request that HTTPClient is sending using
WireShark and indeed the format of the request is not correct. The
headers are repeated twice and the body too is not correctly placed
(unfortunately I cant point out the exact mistake, but comparing it with
a request that a soap client sends its different and seeming incorrect).
>>>
>>> Is anybody aware of any problems related to StringEntity? Or maybe
any other way I can send xml data using HttpPost method in HttpClient
4.0 API.
>>>
>>> Any help would be highly appreciated, I am behind my deadline on
this task :(.

>>>
>>> Thanks!!
>>>
>> Turn off 'expect-continue' handshaking.
>>
>> Oleg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
>> For additional commands, e-mail: httpclient-users-help@...
>>
>>
>>
>>
>> Add whatever you love to the Yahoo! India homepage. Try now!

http://in.yahoo.com/trynew
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
>
>
> The INTERNET now has a personality. YOURS! See your Yahoo!
Homepage. http://in.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Sending SOAP request using HTTPPost (HttpClient 4.0)

2009-11-09T13:39:51Z

arpita dhundia wrote:
> I tried setting the expect 100 continue param false but the problem still persists..
>
> I am performimg very simple stpes, using NTLm authentication, creating an HTTPPost object and attaching a StringEntity object to it, on which I have written the xml data.
> Wireshark shows that the post data is not in the right format, hence the recieving server sends back an HTTP 400 error.
> I am not sure what I am doing wrong, or maybe what can I do to avoid this error.
>

Doe not use Wireshark. Use wire log of HttpClient instead

http://hc.apache.org/httpcomponents-client/logging.html

Oleg

> Please help.
>
> Thanks,
> Arpita
>
>
>
> --- On Sat, 7/11/09, Thierry Boileau <thboileau@...> wrote:
>
> From: Thierry Boileau <thboileau@...>
> Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)
> To: "HttpClient User Discussion" <httpclient-users@...>
> Date: Saturday, 7 November, 2009, 5:03 PM
>
> Hello,
>
> you can find documentation here
> http://hc.apache.org/httpcomponents-client/tutorial/pdf/httpclient-tutorial.pdf
>
> best regards,
> Thierry Boileau
>
>> Thanks for the reply Oleg, could you guide a little how can I do that?
>>
>> Regards,
>> Arpita
>>
>> --- On Sat, 31/10/09, Oleg Kalnichevski <olegk@...> wrote:
>>
>> From: Oleg Kalnichevski <olegk@...>
>> Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)
>> To: "HttpClient User Discussion" <httpclient-users@...>
>> Date: Saturday, 31 October, 2009, 4:40 AM
>>
>> arpita dhundia wrote:
>>> Hello Folks,
>>>
>>> I have run into a very odd problem.
>>> I have to send a SOAP (xml data over HTTP Post) request to another server behind NTLM authentication. I am using HttpClient 4.0 for that.
>>> The NTLM authentication works fine but when I try to send the xml data using StringEntity and set that Entity to the HTTPPpost Object, I am returned 400 error code, meaning "bad request".
>>> I tried to see the exact request that HTTPClient is sending using WireShark and indeed the format of the request is not correct. The headers are repeated twice and the body too is not correctly placed (unfortunately I cant point out the exact mistake, but comparing it with a request that a soap client sends its different and seeming incorrect).
>>>
>>> Is anybody aware of any problems related to StringEntity? Or maybe any other way I can send xml data using HttpPost method in HttpClient 4.0 API.
>>>
>>> Any help would be highly appreciated, I am behind my deadline on this task :(.
>>>
>>> Thanks!!
>>>
>> Turn off 'expect-continue' handshaking.
>>
>> Oleg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
>> For additional commands, e-mail: httpclient-users-help@...
>>
>>
>>
>>
>> Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
>
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Concurrent connections

2009-11-09T13:38:24Z

Mohit Anchlia wrote:
> Currently we have code that does HttpClient client = new HttpClient();
> for every post request. We have around 30 concurrent requests being
> made. I am trying to understand if we use HttpClient this way then
> does it create new connection for every request

Yes, it does. You effectively throw away a potentially reusable
connection after each request execution.

For proper usage of HttpClient connection pooling see:

http://hc.apache.org/httpcomponents-client/tutorial/html/connmgmt.html#d4e596
http://hc.apache.org/httpcomponents-client/tutorial/html/connmgmt.html#d4e629

I mean does it have a max concurrent request limit
> when HttpClient is used in this way?
>
> Also, how do I see or debug how many requests are waiting on
> HttpClient to get a connection?
>

Use wire / context logging

http://hc.apache.org/httpcomponents-client/logging.html

Oleg

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Sending SOAP request using HTTPPost (HttpClient 4.0)

2009-11-09T12:57:18Z

I tried setting the expect 100 continue param false but the problem still persists..
I am performimg very simple stpes, using NTLm authentication, creating an HTTPPost object and attaching a StringEntity object to it, on which I have written the xml data.
Wireshark shows that the post data is not in the right format, hence the recieving server sends back an HTTP 400 error.
I am not sure what I am doing wrong, or maybe what can I do to avoid this error.

Please help.

Thanks,
Arpita

--- On Sat, 7/11/09, Thierry Boileau <thboileau@...> wrote:

From: Thierry Boileau <thboileau@...>
Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)
To: "HttpClient User Discussion" <httpclient-users@...>
Date: Saturday, 7 November, 2009, 5:03 PM

Hello,

you can find documentation here
http://hc.apache.org/httpcomponents-client/tutorial/pdf/httpclient-tutorial.pdf

best regards,
Thierry Boileau

> Thanks for the reply Oleg, could you guide a little how can I do that?
>
> Regards,
> Arpita
>
> --- On Sat, 31/10/09, Oleg Kalnichevski <olegk@...> wrote:
>
> From: Oleg Kalnichevski <olegk@...>
> Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)
> To: "HttpClient User Discussion" <httpclient-users@...>
> Date: Saturday, 31 October, 2009, 4:40 AM
>
> arpita dhundia wrote:
>> Hello Folks,
>>
>> I have run into a very odd problem.
>> I have to send a SOAP (xml data over HTTP Post) request to another server behind NTLM authentication. I am using HttpClient 4.0 for that.
>> The NTLM authentication works fine but when I try to send the xml data using StringEntity and set that Entity to the HTTPPpost Object, I am returned 400 error code, meaning "bad request".
>> I tried to see the exact request that HTTPClient is sending using WireShark and indeed the format of the request is not correct. The headers are repeated twice and the body too is not correctly placed (unfortunately I cant point out the exact mistake, but comparing it with a request that a soap client sends its different and seeming incorrect).
>>
>> Is anybody aware of any problems related to StringEntity? Or maybe any other way I can send xml data using HttpPost method in HttpClient 4.0 API.
>>
>> Any help would be highly appreciated, I am behind my deadline on this task :(.
>>
>> Thanks!!
>>
>
> Turn off 'expect-continue' handshaking.
>
> Oleg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
>
>
> Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/

Concurrent connections

2009-11-09T08:24:02Z

Currently we have code that does HttpClient client = new HttpClient();
for every post request. We have around 30 concurrent requests being
made. I am trying to understand if we use HttpClient this way then
does it create new connection for every request or could it have some
kind of throttling? I mean does it have a max concurrent request limit
when HttpClient is used in this way?

Also, how do I see or debug how many requests are waiting on
HttpClient to get a connection?

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Sending SOAP request using HTTPPost (HttpClient 4.0)

2009-11-07T07:37:45Z

arpita dhundia wrote:
> Thanks for the reply Oleg, could you guide a little how can I do that?
>
> Regards,
> Arpita
>

DefaultHttpClient httpclient = new DefaultHttpClient();
httpclient.getParams().setBooleanParameter(CoreProtocolPNames.USE_EXPECT_CONTINUE,
false);

Oleg

> --- On Sat, 31/10/09, Oleg Kalnichevski <olegk@...> wrote:
>
> From: Oleg Kalnichevski <olegk@...>
> Subject: Re: Sending SOAP request using HTTPPost (HttpClient 4.0)
> To: "HttpClient User Discussion" <httpclient-users@...>
> Date: Saturday, 31 October, 2009, 4:40 AM
>
> arpita dhundia wrote:
>> Hello Folks,
>>
>> I have run into a very odd problem.
>> I have to send a SOAP (xml data over HTTP Post) request to another server behind NTLM authentication. I am using HttpClient 4.0 for that.
>> The NTLM authentication works fine but when I try to send the xml data using StringEntity and set that Entity to the HTTPPpost Object, I am returned 400 error code, meaning "bad request".
>> I tried to see the exact request that HTTPClient is sending using WireShark and indeed the format of the request is not correct. The headers are repeated twice and the body too is not correctly placed (unfortunately I cant point out the exact mistake, but comparing it with a request that a soap client sends its different and seeming incorrect).
>>
>> Is anybody aware of any problems related to StringEntity? Or maybe any other way I can send xml data using HttpPost method in HttpClient 4.0 API.
>>
>> Any help would be highly appreciated, I am behind my deadline on this task :(.
>>
>> Thanks!!
>>
>
> Turn off 'expect-continue' handshaking.
>
> Oleg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@...
> For additional commands, e-mail: httpclient-users-help@...
>
>
>
>
> Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...

Re: Sending SOAP request using HTTPPost (HttpClient 4.0)

2009-11-07T03:33:49Z

Hello,

you can find documentation here
http://hc.apache.org/httpcomponents-client/tutorial/pdf/httpclient-tutorial.pdf

best regards,
Thierry Boileau

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@...
For additional commands, e-mail: httpclient-users-help@...