mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vishal_Jain <pingvis...@gmail.com>
Subject Re: AsyncHttpClient with no content-length header
Date Wed, 05 Dec 2007 14:57:32 GMT

Thanks Jeff.
have raised a JIRA. https://issues.apache.org/jira/browse/DIRMINA-487

While it is being fixed, is there anything i can look at to fix the issue
(even if temporarily)  ?
would really appreciate if someone can help me work out a fix.

vishal


jgenender wrote:
> 
> Yes, please open a JIRA on this.  According to the HTTP spec, anything
> with content should have a content line.  However, there does appear to
> be a site that is not compliant (http://www.toptable.co.uk/) and
> probably more... thus we could fall back to reading until there is no
> more data.  However, this concerns me as a possible buffer/memory
> problem (it would then be easy to crash a Mina client).  Anyone have an
> opinion on this?
> 
> Jeff
> 
> Vishal_Jain wrote:
>> Is there a JIRA id for this issue ? 
>> or any workarounds ?
>> 
>> vishal
>> 
>> 
>> berdim99 wrote:
>>> Hi.
>>> It seems that AsyncHttpClient fails to decode a web page in which the
>>> web-server doesn't send a content-length header.
>>> What happens is that the callback is called with a null content, after
>>> which the decoder throws an exception because it thinks that the rest of
>>> the incoming data are of a new HTTP response (but they are actually the
>>> previous response content).
>>> (Such web site is http://www.toptable.co.uk/).
>>>
>>> Any help is appreciated.
>>> Micha.
>>>
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/AsyncHttpClient-with-no-content-length-header-tf4723565s16868.html#a14173229
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.


Mime
View raw message