Re: Proxy server policy [was Re: gated]

["Adam P. Harris" <apharris@onshore.com>]

[You (Adrian Bridgett)]
>We should also standardize the environment variables that are used. Once
>again, if the program doesn't support environment variables, tough -
>although of course maintainers are encouraged to "fix" the programs :-)

Maybe just enforce the standards that are kinda sorta already there, or 
even just forward bugs upstream if these are not supported?

$http_proxy env variable is supported by lynx, W3 mode in Emacsen, and
Mosaic flavors.  Also don't forget WWW_HOME as your home page.

I think there's not really much way we can get them to get netscape to 
respect this; I don't think it's worth it to munge thru the (quite 
volatile) netscape preferences either.

>If people could be kind enough to email sample proxy configurations to me
>(ones that are supported by some non-customized program), then I'll come up
>with a proposed scheme. I'll include some sample code to make it easier for
>maintainers to convert a program.

Well, the less work the better ;)

BTW, my home scheme doesn't really fit into your map.  This is for squid, 
in this case, running on localhost:

gopher_proxy=http://localhost:3128/
http_proxy=http://localhost:3128/
ftp_proxy=http://localhost:3128/  

FWIW, there's also an experimental Linux feature, transparent proxy, I 
think, which could automatically redirect outbound HTTP requests to a 
local httpd cache.

.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .