t;> 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/).
>>>
>>> A
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,
t;> 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).
&g
e 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#a14166396
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
cha.
>
--
View this message in context:
http://www.nabble.com/AsyncHttpClient-with-no-content-length-header-tf4723565s16868.html#a14166028
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
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#a13505012
Sent fro
