Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-05 Thread Angus Robertson - Magenta Systems Ltd
> Actually I tested with our Linksys routers admin page... So how to do you propose the fix you are requesting is tested? Do many people use ICS to access a router admin page without the correct password, I'm surprised it gave a 401 error and not just another login window. My two Linksys rout

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-05 Thread Fastream Technologies
Actually I tested with our Linksys routers admin page... On Wed, Oct 5, 2011 at 09:37, Angus Robertson - Magenta Systems Ltd < an...@magsys.co.uk> wrote: > > To elaborate: You need a page with no content-length and no chunked > > encoding that returns 401 to see it. > > And the URL of that example

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-04 Thread Angus Robertson - Magenta Systems Ltd
> To elaborate: You need a page with no content-length and no chunked > encoding that returns 401 to see it. And the URL of that example page is what? Or are you expecting someone to create a badly formatted example page for you? Angus -- To unsubscribe or change your settings for TWSocket m

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-04 Thread Fastream Technologies
To elaborate: You need a page with no content-length and no chunked encoding that returns 401 to see it. Best Regards, SZ On Wed, Oct 5, 2011 at 07:07, Fastream Technologies wrote: > Here is a screenshot of the issue as a picture is worth a thousand words: > http://www.fastream.com/ics/ICSHTTPCLI

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-04 Thread Fastream Technologies
Here is a screenshot of the issue as a picture is worth a thousand words: http://www.fastream.com/ics/ICSHTTPCLI.png Regards, SZ On Wed, Oct 5, 2011 at 06:26, Fastream Technologies wrote: > Dear Arno, > > The new problem happens with GET on pages with no content-length and no > chunked-encoding.

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-04 Thread Fastream Technologies
Dear Arno, The new problem happens with GET on pages with no content-length and no chunked-encoding. This bug had once been there, and then was fixed. Now it happens again. Please try against such a page with Httptst demo and you will see that the OnDocData is never called but instead all the data

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-04 Thread Yuri Semenov
>>BTW Yuri, your code lacks the latest 7.18 bug fix by us (me and Arno). Regards, Sorry, again me. 7.18 fix not for my problem. Try check this page with v7.18 or any other version with httpoEnableContentCoding option. THttpCli can't decode this gzip - http://ws.audioscrobbler.com/2.0/?method=artis

Re: [twsocket] THttpCli bug with no-content-length and no chunckedencoding

2011-10-04 Thread Arno Garrels
Fastream Technologies wrote: > We had actually paid for HttpCli bug fixes to Arno. I hope he will > show up and fix it soon. We do not use content coding so I do not > think Yuri's fix would work. I made your test case working by a fix of chunked decoding. So what actually is the problem now? With