Re: LWP .01
Joel Scotkin (scotkin_joel@jpmorgan.com)
Tue, 18 Jul 1995 16:27:23 -0400 (EDT)
Thanks, Martijn - I'll take a look at your latest patch...
Roy wrote:
>BTW, I just invented a new mechanism for URI resolution that may
>replace the existing proxy_* environment variables.
>I need to finish the specification, but it uses a client configuration
>table (what I call a "URI Resolution Table"). See if you can guess
>how it works just by looking at the format:
>
>=================
>www-uri-table/0.1
>#
>#PREFIX HANDLER REPLACEMENT AUTH
>#
>wais: proxy http://wais.com/ Y
>ietf: replace file:/home/roy/ietf N
>ietf:/rfc replace ftp://ftp.ics.uci.edu/pub/ietf N
>ietf: replace http://ds.internic.net N
>http://info.cern.ch replace http://www.w3.org Y
>http://hardcore.com internal block Y
>http: internal wwwhttp Y
>ftp: internal wwwftp Y
>news: internal wwwnews Y
>gopher: internal na Y
>telnet: external (xterm -c "telnet %HOST %PORT") Y
>=================
Does this also handle the inverse case for things like no_proxy? It might
depend on whether the file is parsed top down, so that later items override
earlier ones. Not to mention wildcards...
The case I am thinking of is what we have here at work - we are behind a
firewall, and we maintain web servers for internal use, and let people
proxy out. So, we would want to say something like:
http: proxy http://gateway.jpmorgan.com/
http://*.jpmorgan.com internal wwwhttp
meaning that everything should be proxied *except* .jpmorgan.com requests.
Currently, most clients can handle this with a (single!) no_proxy field,
and most proxies can also (when doing proxy chaining).
Would something like this be doable?
Joel