WWW Proxy Server
WWW Guidelines:
Multiple WWW proxy services can be configured on different ports. All services
are uniquely named for easy identification.
Caching
The WinGate 2 WWW Proxy provides HTTP caching. HTTP Caching is the process of
storing recently accessed graphics, HTML documents or other files from the
Internet on the WinGate machine, to allow faster retrieval the next time they are
requested from any LAN machine.
WinGate will only cache HTTP requests (i.e not FTP URLs), that use the
See
The WinGate 2 WWW proxy is configurable to allow both Proxy and Non proxy requests. This means there are two modes of operation. This allows the proxy
to integrate seamlessly with Web servers.
Proxy requests: If a proxy request is made on the port on which a HTTP Proxy server is
running, the request is treated in the normal way. If the request is a valid proxy
request, HTTP access is granted. If a non-proxy request is made, access is denied.
Non proxy requests: In the case of a non-proxy request, you have options of what to do with that
request. A request can be piped to a Web server, or a page served from disk.
Site retry order
If the requested URL does not exist, the WWW proxy will now attempt to connect
to URLs based around that name. This allows one to simply type
http://site/
http://site.com/
http://www.site.com/
etc…
To add site searches see
See also
Cache Management
The WWW proxy supports HTTP, Secure HTTPS and FTP.
HTTP is used for World Wide Web browsing and many other programs.
The usual WWW proxy port is 80. This is configurable.
Web Servers also usually run on port 80.
The WWW proxy allows CERN (i.e.: passive browser) FTP. You can also use SOCKS for this if you prefer.
The proxy allows Cascading and Non-Proxy request handling.