Article View: borland.public.cppbuilder.internet.socket
Article #1229Re: Bug in TIdTCPClient ???
From: Umberto Spagnoli
Date: Mon, 12 Mar 2007 16:51
Date: Mon, 12 Mar 2007 16:51
4 lines
1136 bytes
1136 bytes
Sorry.. my fault With a network sniffer I found out that the reply comes from the server. I was sure that the server didn't reply, but it wasn't true.
Technical Details
Message-ID:
<45f584b1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<45f530f7@newsgroups.borland.com> <45f580f6@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,ee03d59ef261bda0 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Umberto Spagnoli" <jumby@tiscali.it> Newsgroups: borland.public.cppbuilder.internet.socket References: <45f530f7@newsgroups.borland.com> <45f580f6@newsgroups.borland.com> Subject: Re: Bug in TIdTCPClient ??? Date: Mon, 12 Mar 2007 17:51:01 +0100 Lines: 7 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 217.133.112.50 Message-ID: <45f584b1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1173718193 217.133.112.50 (12 Mar 2007 09:49:53 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail