Trouble with proxies

[befletch at my-dejanews.com]

In article <5lzp3qafkj.fsf at eric.cnri.reston.va.us>,
  Guido van Rossum <guido at eric.cnri.reston.va.us> wrote:
> A quick lookup in errno.errorcode shows that that error is
> WSAECONNRESET, in other words the connection is reset by the server.
> This apparently happens after the proxy has read your headers.  Could
> it be that the proxy server requires some kind of magic header?  Ask
> the sysadmin who is responsible for the proxy.  At least find out what
> the proxy software is, you can probably find the specs on the web....
>
> If you have a way to snoop network packets, it would be interesting to
> see what traffic happens when your regular browser (IE or netscape)
> connects to the proxy from the same client machine (I'm assuming that
> works!).

The proxy server is WinProxy Lite, V2.1.  It is running on an NT4 server.
Yes, IE and Netscape both work fine through the proxy server, and no, the
sysadmin doesn't know anything more about WinProxy than how to install it
and configure it for normal http/ftp/smtp/pop3 clients.

Following suggestions from several kind people, I have also tried the
following:

import os, urllib

os.environ['http_proxy'] = "http(colon-slash-slash)10.187.200.230"

f = urllib.urlopen('http://www.python.org')

data = f.read()

This gets as far as the f.read() call before it fails in the same fashion.
Appending ":80" or ":8080" to the proxy URL yield the same results, too.
I'm going to try to contact the WinProxy folks and see if they have any
insight into this problem, but if anyone here can help, it would of course
be appreciated.

Thanks,
- Bruce

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own