On 2010-09-08 11:50, Oleg Kalnichevski wrote:
> On Wed, 2010-09-08 at 11:38 +0200, Michel Onoff wrote:
>> On 2010-09-07 21:23, Oleg Kalnichevski wrote:
>>> On Tue, 2010-09-07 at 18:20 +0200, Michel Onoff wrote:
By specification, HTTP response 304 Not Modified has no entity.
However,
On Wed, 2010-09-08 at 11:38 +0200, Michel Onoff wrote:
> On 2010-09-07 21:23, Oleg Kalnichevski wrote:
> > On Tue, 2010-09-07 at 18:20 +0200, Michel Onoff wrote:
> >> By specification, HTTP response 304 Not Modified has no entity.
> >>
> >> However, getEntity() on the BasicHttpResponse still return
On 2010-09-07 21:23, Oleg Kalnichevski wrote:
> On Tue, 2010-09-07 at 18:20 +0200, Michel Onoff wrote:
>> By specification, HTTP response 304 Not Modified has no entity.
>>
>> However, getEntity() on the BasicHttpResponse still returns a non-null
>> entity. Trying to getContent() and read() then bl
On Tue, 2010-09-07 at 18:20 +0200, Michel Onoff wrote:
> By specification, HTTP response 304 Not Modified has no entity.
>
> However, getEntity() on the BasicHttpResponse still returns a non-null
> entity. Trying to getContent() and read() then blocks. The same happens
> if one tries to send the r
By specification, HTTP response 304 Not Modified has no entity.
However, getEntity() on the BasicHttpResponse still returns a non-null
entity. Trying to getContent() and read() then blocks. The same happens
if one tries to send the response with
HttpServerConnection.sendResponseEntity(response).