ClientProtocolException

2012-01-19 Thread Mohit Anchlia
When we do a POST we are getting the following exception? Transfer-encoding is set chunked. Not sure why it's throwing this exception org.apache.http.client.ClientProtocolException at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822) at org.apach

Re: ClientProtocolException

2012-01-19 Thread William Speirs
I think because there is a modifier which is setting this header, then you're trying to do it manually and getting this exception. What happens if you remove the manual setting of the header? Bill- On Jan 19, 2012 6:02 PM, "Mohit Anchlia" wrote: > When we do a POST we are getting the following e

Re: ClientProtocolException

2012-01-20 Thread Oleg Kalnichevski
On Thu, 2012-01-19 at 15:02 -0800, Mohit Anchlia wrote: > When we do a POST we are getting the following exception? > Transfer-encoding is set chunked. Not sure why it's throwing this > exception > > org.apache.http.client.ClientProtocolException > at > org.apache.http.impl.client.Abstrac

Re: ClientProtocolException

2012-01-20 Thread Mohit Anchlia
I agree, didn't realize that code was setting it manually. On Fri, Jan 20, 2012 at 1:59 AM, Oleg Kalnichevski wrote: > On Thu, 2012-01-19 at 15:02 -0800, Mohit Anchlia wrote: >> When we do a POST we are getting the following exception? >> Transfer-encoding is set chunked. Not sure why it's throwi

ClientProtocolException for 204 No Content as response header

2014-07-12 Thread srikalyan swayampakula
Hi, I am getting a ClientProtocolException for a delete request. The response is "204 No Content" and seems to be a bug in httpclient. I am creating the transport like this transport = new ApacheHttpTransport(); final RequestConfig defaultRequestConfig = RequestConf

Re: ClientProtocolException for 204 No Content as response header

2014-07-12 Thread srikalyan swayampakula
Also, I forgot to mention this. This seems to happen with alternative calls. On Sat, Jul 12, 2014 at 8:18 AM, srikalyan swayampakula < srikalyansswa...@gmail.com> wrote: > > Hi, > > I am getting a ClientProtocolException for a delete request. The response > is "204 No

Re: ClientProtocolException for 204 No Content as response header

2014-07-13 Thread Oleg Kalnichevski
On Sat, 2014-07-12 at 08:18 -0700, srikalyan swayampakula wrote: > Hi, > > I am getting a ClientProtocolException for a delete request. The response > is "204 No Content" and seems to be a bug in httpclient. > > I am creating the transport like this > > t

Re: ClientProtocolException for 204 No Content as response header

2014-07-13 Thread srikalyan swayampakula
. I will dig deeper and let you know if there is an issue and really sorry if this a false alarm. Thank you. On Sun, Jul 13, 2014 at 4:43 AM, Oleg Kalnichevski wrote: > On Sat, 2014-07-12 at 08:18 -0700, srikalyan swayampakula wrote: > > Hi, > > > > I am getting

Re: ClientProtocolException for 204 No Content as response header

2014-07-14 Thread srikalyan swayampakula
140 PDT 2014 | "ajp-bio-8009"-exec-2 | > org.apache.http.message.BasicLineParser | DEBUG | Testing the line: > ^_^H^@^@^@^@^@^@^@^C^@^@^@^@^@^@^@^@^@HTTP/1.1 204 No Con > tent the cursor is: [0>0>43] the protname is: HTTP > Sun Jul 13 00:51:06.140 PDT 2014 | "ajp-bio-80

Re: ClientProtocolException for 204 No Content as response header

2014-07-14 Thread srikalyan swayampakula
; >>if (this.log.isDebugEnabled()) { >> this.log.debug("The value of ok after for is : " + >> buffer.toString() + " the cursor is: " + cursor >> + " the protname is: " + protoname +" the index >