[PROXYPER] HTTP proxy different in clients?
jlawson at bovine.net
Thu Dec 16 02:50:36 EST 1999
Yes, by necessity the networking code between the client and proxy have
always been different codebases, since the proxy was written to have greater
performance and transfer larger batches of operations together. There were
some recent changes to the proxy networking codebase in an attempt to
further increase performance, however many people are encountering
incompatibilities with some http-proxy systems, which I will attempt to
address in the next release.
Jeff Lawson http://www.bovine.net/ http://www.cs.hmc.edu/~jlawson/
Jeffrey_Lawson at alumni.hmc.edu jlawson at bovine.net bovine at distributed.net
Programmer, Developer, Mascot, Founder of the largest computer on earth!
Don't waste those cycles! Put them to use! http://www.distributed.net/
----- Original Message -----
From: "Andy Key" <akey123 at hotmail.com>
To: <proxyper at lists.distributed.net>
Sent: Monday, December 13, 1999 5:51 AM
Subject: [PROXYPER] HTTP proxy different in clients?
> Personal Proxy (build 311) on Windows NT (x86).
> I've got a small isolated network that I've been feeding via a personal
> proxy. I would stop the proxy, copy the files over to a machine with a
> permanent connection, fire up the personal proxy. As soon as it connected
> and completed updating its buffers, I'd shut it down, and move it back to
> the isolated network.
> All was well and good until recently. For some reason (possibly even a
> change in the firewall configuration), the personal proxy is no longer
> to get through the firewall, even though the clients (v2.8002-446 client
> Win32) that I have installed on machines with a permanent connection can
> connect via HTTP tunneling. Does the personal proxy use different code
> connecting than the normal clients?
To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net
More information about the proxyper