On Fri, 2010-10-15 at 16:56 +0530, Supun Kamburugamuva wrote:
> On Fri, Oct 15, 2010 at 10:38 AM, Asankha C. Perera wrote:
>
> >
> > In my case there is no stack trace. The browser is the client. Browser
> >> waits
> >> for the data to come but I can clearly see that the page has transferred
> >>
On Fri, Oct 15, 2010 at 10:38 AM, Asankha C. Perera wrote:
>
> In my case there is no stack trace. The browser is the client. Browser
>> waits
>> for the data to come but I can clearly see that the page has transferred
>> to
>> the browser. This means that the chunking is incorrect and browser th
In my case there is no stack trace. The browser is the client. Browser waits
for the data to come but I can clearly see that the page has transferred to
the browser. This means that the chunking is incorrect and browser thinks
there is more data to come.
When I force content length to the brows
On Thu, Oct 14, 2010 at 7:49 PM, Asankha C. Perera wrote:
> Hi Supun, Oleg
>
> When a response is written back to the client the chunking was incorrect.
>> All the communications were done through HTTPS. Do you think the same
>> problem is there in the client side of the HTTPCore NIO as well?
>>
On Thu, 2010-10-14 at 20:25 +0530, Asankha C. Perera wrote:
> Hi Oleg
> > Apparently the limit value on the ByteArray instance is miscalculated
> > for some reason. At this moment I can't think of a cause leading to such
> > condition. So, a reproducer would be very help.
> >
> // subt
Hi Oleg
'avail' is not checked for being negative after this line
avail -= 10;
Damn!
Damn indeed! I overlooked the possibility of it being negative and was
looking for ways how it could have exceeded the limit :D.. Shows the
value of more than one pair of eyes :)
Could you please raise a
Hi Oleg
Apparently the limit value on the ByteArray instance is miscalculated
for some reason. At this moment I can't think of a cause leading to such
condition. So, a reproducer would be very help.
// subtract the length of the longest chunk header
// 12345678\r\n
av
On Thu, 2010-10-14 at 16:40 +0200, Oleg Kalnichevski wrote:
> On Thu, 2010-10-14 at 19:49 +0530, Asankha C. Perera wrote:
> > Hi Supun, Oleg
> > > When a response is written back to the client the chunking was incorrect.
> > > All the communications were done through HTTPS. Do you think the same
On Thu, 2010-10-14 at 19:49 +0530, Asankha C. Perera wrote:
> Hi Supun, Oleg
> > When a response is written back to the client the chunking was incorrect.
> > All the communications were done through HTTPS. Do you think the same
> > problem is there in the client side of the HTTPCore NIO as well?
On Thu, 2010-10-14 at 19:40 +0530, Supun Kamburugamuva wrote:
> Hi Oleg,
>
> We moved to the trunk and it was working fine. So the patch has fixed the
> issue. Then we faced another problem. When a response is written back to the
> client the chunking was incorrect. All the communications were don
Hi Supun, Oleg
When a response is written back to the client the chunking was incorrect. All
the communications were done through HTTPS. Do you think the same problem is
there in the client side of the HTTPCore NIO as well?
I've encountered the following stack trace with 4.1-beta1 from a us
Hi Oleg,
We moved to the trunk and it was working fine. So the patch has fixed the
issue. Then we faced another problem. When a response is written back to the
client the chunking was incorrect. All the communications were done through
HTTPS. Do you think the same problem is there in the client si
Hi Oleg,
Thanks for the quick answer. I'll try to migrate to the latest trunk and see
how it goes.
Thanks,
Supun..
On Wed, Oct 13, 2010 at 7:32 PM, Oleg Kalnichevski wrote:
> On Wed, 2010-10-13 at 18:06 +0530, Supun Kamburugamuva wrote:
> > I'm trying to read a HTTPs response coming from tomca
On Wed, 2010-10-13 at 18:06 +0530, Supun Kamburugamuva wrote:
> I'm trying to read a HTTPs response coming from tomcat using Http Core NIO.
> But it seems that the chunked encoding is not handled properly. I cannot say
> weather chunking is incorrect in Tomcat or NIO because the communication is
>
I'm trying to read a HTTPs response coming from tomcat using Http Core NIO.
But it seems that the chunked encoding is not handled properly. I cannot say
weather chunking is incorrect in Tomcat or NIO because the communication is
happening through HTTPs. Is there any known issues like this in Http C
15 matches
Mail list logo
