On Mon, May 20, 2013 at 08:21:56AM -0700, Tony Anecito wrote: > Thanks David, > > I am curious does anyone know if chunked encoding by default was enabled in > httpclient sometime after httpclient 3.1? I see hints of it when I google. > > Thanks, > -Tony > >
Chunk content coding was always on since early 2.x versions. Support for chunk transfer encoding is mandated by the HTTP/1.1 spec. Oleg > > > ________________________________ > From: David Motes <[email protected]> > To: HttpClient User Discussion <[email protected]>; Tony Anecito > <[email protected]> > Sent: Monday, May 20, 2013 7:49 AM > Subject: Re: Truning off Chunked Encoding... > > > Use the setChunked method on the entity which defines the content. > There is a content size limit of around 2GB if you do not use chunked > transfer. > > DefaultHttpClient cli = new DefaultHttpClient(); > HttpPut method = new HttpPut(url); > InputStreamEntity reqEntity = new InputStreamEntity(pmis, -1); > reqEntity.setContentType("application/octet-stream"); > reqEntity.setChunked(false); > > method.setEntity(reqEntity); > resp = cli.execute(method); > > > On Sun, May 19, 2013 at 5:19 PM, Tony Anecito <[email protected]> wrote: > > > Hi All, > > > > I recently upgraded from http client 3.1 to 4.2.5 and discovered that some > > http proxies (earlier version squid proxy does not supported it) will not > > work with 4.2.5 due to not supporting chunked encoding. > > > > So for now how do I tell 4.2.5 not to use chunked encoding? I do not have > > control over proxies to get them to upgrade that do not support chunked > > encoding. > > > > Thanks, > > -Tony --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
