URI resolution table
Roy Fielding (fielding@beach.w3.org)
Tue, 18 Jul 1995 22:11:50 -0400
>>=================
>>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 Y
>>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 rule is that it takes the first matching prefix (top to bottom),
and stops at the first 2xx answer, or the first authoritative (AUTH)
non-5xx answer.
>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
Well, I was not going to include any wildcard characters, but
http://fred.jpmorgan.com internal wwwhttp Y
http://wilma.jpmorgan.com internal wwwhttp Y
http://barney.jpmorgan.com internal wwwhttp Y
http: proxy http://gateway.jpmorgan.com/ Y
would do that.
....Roy T. Fielding Department of ICS, University of California, Irvine USA
Visiting Scholar, MIT/LCS + World-Wide Web Consortium
(fielding@w3.org) (fielding@ics.uci.edu)