Re: HTTPS environment variable
From: Robert Brown (brownr_at_gmail.com)
Date: 2 Dec 2004 11:14:24 -0800
Thats exactly what I was looking for. One problem. I have to find
some way to make it authenticate as well.
Thanks for the suggestion. Never knew about rinetd. Thanks for the
email@example.com (Peter T. Breuer) wrote in message news:<firstname.lastname@example.org>...
> email@example.com wrote:
> > I knew I'd get busted for this. What I'm looking for is something
> > equivalent to going into the Internet Options in Windows (there, I said
> > it) and setting the proxy settings. Basically, I want every
> > application that tries to go out over port 443 to go through the proxy
> > server. I'm looking for a way to set that up globally.
> In a certain sense, there isn't one - not at the applicaton level.
> There is no single thing that every application looks at to decide if it
> should use a proxy or not. Yu want to set every application
> individually if you decide to work at the application level.
> OTOH there is nothing to stop you rerouting at a network level.
> However, I believe you are mischaracterizing .. what do you mean "out
> over port 443"? Do you have the impression that there is a port 443 on
> YOUR machine that is used to talk via https?
> No. Wrong. The source port is irrelevant. The port 443 is that of the
> REMOTE machine.
> You can certainly redirect requests to remote port 443s to a proxy
> server of yours. Indeed, that is precisely what "rinetd" is for. It
> helps you with that (of course you could do it yourself via iptables).
> Just install it, edit rinetd.conf to taste, and start it.