I finally managed to track what is happening here - in Internet options, if
"Use HTTP 1.1" is unchecked, this behavior occurs when there is no
"Connection:" in the header, thus causing this problem when virtual pages
are sent. 

On 22/5/2005 16:11:43, Francois PIETTE ([EMAIL PROTECTED]) wrote:
> > The only questions that remain are: why does this happen only with
> virtual
> > pages and not with documents?
> You can easily built a dynamic page that return exactly the same
> informations than a static page. If you try that, verify using a sniffer
> that the output is exactly the same.
> > Why does this happen only with IE and not with
> > FireFox?
> For example, the computer has been infected by a malware/spyware that
> affect
> only IE. Some are hiffen behind a toolbar installed in IE. Use Microsoft
> AntiSpy to detect those beast that are not detected by anti-virus.
> --
> ----- Original Message -----
> From: "Bruno Sonnino" <[EMAIL PROTECTED]>
> To: <>
> Sent: Sunday, May 22, 2005 7:38 PM
> Subject: Re: Re[2]: [twsocket] Connection not closed in WebServer with IE
> > I begin to think that this is the problem - I was thinking two options:
> > something with the Brazilian Portuguese version of IE, or something with
> a
> > program that intercepts communications, like an antivirus.
> > The only questions that remain are: 

To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to