[twsocket] contentrange problem with proxy

2011-11-15 Thread Wanao - Jean DELAGOUTTE
There is a problem with ContentRange when we use proxy Example : I wan’t donwload only the first Mo of a 5Mo file Httpcli.ContentRangeStar := 0 ; Httpcli.ContentRangeEnd :=1048575 ; Httpcli.get ; If we don't use proxy i have a downloaded file size 1Mo. But if i use proxy with the same code

[twsocket] NTLM proxy auth problem without login+password

2011-11-15 Thread Wanao - Jean DELAGOUTTE
Hello, I'm using the proxy software SquidNT with plugin for NTLM authentification. With Internet explorer, i don't have problem if i navigate with a domain user, it don't ask login+password. if i navigate with a no domain user, Internet explorer ask me a login+password for navigation. All that

[twsocket] RE : contentrange problem with proxy

2011-11-15 Thread Wanao - Jean DELAGOUTTE
It seems the mailinglist is not accept join file so the patch is : Index: Delphi/Vc32/OverbyteIcsHttpProt.pas === --- Delphi/Vc32/OverbyteIcsHttpProt.pas (révision 814) +++ Delphi/Vc32/OverbyteIcsHttpProt.pas (copie de travail) @@

[twsocket] HttpAppSrv1, ClientDisconnect : DeleteSession when user exit from his browser?

2011-11-15 Thread Bruno Mannina
Dear Users, I try to use the sample HttpAppSrv provide with ICS and I would like to add a little thing: If the user closes the browser, I would like to: - 1st: Display the disconnection - 2nd: delete his sessiondata But If I test in local (127.0.0.1...) what I have (see below): - no erreur

Re: [twsocket] HttpAppSrv1, ClientDisconnect : DeleteSession when user exit from his browser?

2011-11-15 Thread Bruno Mannina
Sorry, please forgot my question, in fact I understand know, my prog enters in the Disconnect proc every 10s (KeepAlive param) so it's not the solution and it's not the right way ! sincerely Bruno Le 15/11/2011 14:54, Bruno Mannina a écrit : Dear Users, I try to use the sample HttpAppSrv

Re: [twsocket] Major bug in first ICS FireMonkey / MacOS beta

2011-11-15 Thread Arno Garrels
Arno Garrels wrote: Hi, I should have tested more carefully, sorry for that. After some stress tests with the webserver for MacOS I hit a bug today that I do not understand. Once in some state Accept() returns a socket handle with a port number that doesn't match the port number of the