-#############################################################################
-# Forwarding
-#############################################################################
-#
-#
-# This feature allows routing of HTTP requests via multiple proxies.
-# It can be used to better protect privacy and confidentiality when
-# accessing specific domains by routing requests to those domains
-# to a special purpose filtering proxy such as lpwa.com
-#
-# It can also be used in an environment with multiple networks to route
-# requests via multiple gateways allowing transparent access to multiple
-# networks without having to modify browser configurations.
-#
-# Also specified here are SOCKS proxies. We support SOCKS 4 and SOCKS 4A.
-# The difference is that SOCKS 4A will resolve the target hostname using
-# DNS on the SOCKS server, not our local DNS client.
-#
-# The syntax of each line is
-#
-# forward target_domain[:port] http_proxy_host[:port]
-# forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]
-# forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]
-#
-# If http_proxy_host is ".", then requests are not forwarded to
-# a HTTP proxy but are made directly to the web servers.
-#
-# Lines are checked in turn, and the last match wins.
-#
-# There is an implicit line equivalent to the following, which specifies that
-# anything not finding a match on the list is to go out without forwarding
-# or gateway protocol; like so:
-# forward .* . # implicit
-#
-# In the following common configuration, everything goes to Lucent's LPWA,
-# except SSL on port 443 (which it doesn't handle)
-# forward .* lpwa.com:8000
-# forward :443 .
-#
-# See the FAQ for instructions on how to automate the login procedure for LPWA.
-# Some users have reported difficulties related to LPWA's use of . as the
-# last element of the domain, and have said that this can be fixed with this:
-# forward lpwa. lpwa.com:8000
-# (NOTE: the syntax for specifiying target_domain has changed since the
-# previous paragraph weas written - it will not work now. More information
-# is welcome.)
-#
-# In this fictitious example, everything goes via an ISP's caching proxy,
-# except requests to that ISP:
-#
-# forward .* caching.myisp.net:8000
-# forward myisp.net .
-#
-# For the @home network, we're told the forwarding configuration is this:
-# forward .* proxy:8080
-# Also, we're told they insist on getting cookies and Javascript, so you need
-# to add home.com to the cookie file. We consider Javascript a security risk;
-# see our page on cookies. Java need not be enabled.
-#
-# In this example direct connections are made to all "internal" domains,
-# but everything else goes through Lucent's LPWA by way of the company's
-# SOCKS gateway to the Internet.
-#
-# forward_socks4 .* lpwa.com:8000 firewall.my_company.com:1080
-# forward my_company.com .
-#
-# This is how you could set up a site that always uses SOCKS but no forwarders
-#
-# forward_socks4a .* . firewall.my_company.com:1080
-#
-# An advanced example for network administrators:
-#
-# If you have links to multiple ISPs that provide various special content to
-# their subscribers, you can configure forwarding to pass requests to the
-# specific host that's connected to that ISP so that everybody can see all
-# of the content on all of the ISPs.
-#
-# This is tricky, but here's a sample:
-#
-# host-a has a PPP connection to isp-a.com
-# host-b has a PPP connection to isp-b.com
-#
-# host-a can run an Internet Junkbuster proxy with forwarding like this:
-# forward .* .
-# forward isp-b.com host-b:8000
-#
-# host-b can run an Internet Junkbuster proxy with forwarding like this:
-# forward .* .
-# forward isp-a.com host-a:8000
-#
-# Now, *anyone* on the Internet (including users on host-a and host-b)
-# can set their browser's proxy to *either* host-a or host-b and
-# be able to browse the content on isp-a or isp-b.
-#
-#
-# Here's another practical example, for University of Kent at
-# Canterbury students with a network connection in their room, who
-# need to use the University's Squid web cache.
-#
-# forward *. ssbcache.ukc.ac.uk:3128 # Use the proxy, except for:
-# forward .ukc.ac.uk . # Anything on the same domain as us
-# forward * . # Host with no domain specified
-# forward 129.12.*.* . # A dotted IP on our /16 network.
-# forward 127.*.*.* . # Loopback address
-# forward localhost.localdomain . # Loopback address
-# forward www.ukc.mirror.ac.uk . # Specific host
-#
-#
-# Note: If you intend to chain junkbuster and squid locally, the chain
-# broswer -> squid -> junkbuster is the recommended way.
-#
-# Your squid configuration could then look like this:
-#
-# # Define junkbuster as parent cache
-# cache_peer 127.0.0.1 8000 parent 0 no-query
-#
-# # Define ACL for protocol FTP
-# acl FTP proto FTP
-#
-# # Do not forward ACL FTP to junkbuster
-# always_direct allow FTP
-#
-# # Do not forward ACL CONNECT (https) to junkbuster
-# always_direct allow CONNECT
-#
-# # Forward the rest to junkbuster
-# never_direct allow all
-#