On Mon, Mar 01, 2004 at 03:46:33PM -0500, Richard Bramante wrote:
> Further testing today seems to indicate that it is an issue specific to a
> Win2k, and it is not limited to curl, or a single machine. The latency
> issues where a red herring as well, it just so happens that those
> conditions probably exacerbated the problem.
>
> For those interested, I took curl out of the picture and wrote a simple
> (using blocking calls) winsock app to test with. What I found was that I
> got "special" behavior when connecting to ports 80, 81, and 8080.
[...]
> So, it would appear to me that there is something in the bowels of the
> Win2k TCP/IP that is doing something "funny" with "HTTP-ish" port numbers,
> but I still find it hard to believe.

This sounds like you have a virus scanner configured as a transparent HTTP
proxy on that machine.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved