HTTP Proxy

Description

The HTTP Proxy is a module built into the RouteFinder to redirect HTTP requests from the clients in the LAN and DMZ to the Internet. The HTTP proxy acts as a caching server for web clients, supporting FTP, gopher, and HTTP data objects. Unlike traditional caching software the HTTP proxy keeps meta data and especially hot objects cached in RAM and also caches DNS lookup.

Note : To view/analyze the HTTP proxy logs through WebTrends software, HTTP access has to be enabled in the Administration->Web Admin page and the port number configured for HTTP access has to be used.

Parameters

HTTP Proxy - Status
HTTP Proxy - Transparent
HTTP Proxy - Networks (allowed / denied)
HTTP Proxy - Banner Filter
HTTP Proxy - Java Script Filter
HTTP Proxy - Cookie Filter
URL Categorization - URL Filter
URL Categorization - URL Categories
URL Categorization - Network / Hosts to bypass URL Filtering
Authentication - User Authentication Status
Authentication - Authentication Types
Authentication - Add / Delete Users
HTTP Proxy - Status
Used to enable or disable HTTP Proxying.
HTTP Proxy - Transparent
If enabled the HTTP proxy functions as a transparent proxy. The web clients are unaware that their requests are being transferred through a HTTP Proxy. The web clients need not configure their browser to point to the Proxy server. Also, in the browser settings the HTTP port is configured to port 80 - the default port for the HTTP protocol.
If disabled the HTTP proxy functions as a non-transparent proxy. The browser settings of web clients must be such that they point to the HTTP Proxy, and the HTTP port number must be set to the port on which the HTTP proxy listens to requests. The default port is 3128.
HTTP Proxy - Networks (allowed / denied)
Defines the allowed / denied status for a network / host for access to the HTTP proxy. On clicking the 'Edit' button a list of the defined networks/hosts and the current status is displayed. The status can be changed by clicking the change status option and altering the policy as desired.
HTTP Proxy - Banner Filter
If enabled, all the banners in the web pages are filtered out before the page is forwarded to the web client.
HTTP Proxy - Java Script Filter
If enabled all the Java Script components in the web pages are filtered out before the page is forwarded to the web client.
HTTP Proxy - Cookie Filter
If enabled cookies in the web pages are filtered out before the page is forwarded to the web client.
URL Categorization - URL Filter
If enabled, traffic from defferent URLs can be configured to be filtered / forwarded by the RouteFinder based on their categories.
URL Categorization - URL Categories
Clicking on the edit button allows configuration of the URL categories to be filtered or forwarded.
URL Categorization - Networks / Hosts to bypass URL Filtering
Clicking on the edit button allows configuration of the networks / hosts for which URL Category based filtering will not happen. These networks/hosts will be able to access all sites.
Authentication - User Authentication Status
Used to enable / disable User Authentication. If User Authentication is disabled then the HTTP proxy can be configured to function in the transparent mode.
Authentication - Authentication Types
If the HTTP proxy functions in a non-transparent mode then the authentication mechanism through which user can be authenticated, can be configured. The different authentication types are local, RADIUS and SAM. The user can configure any one of the three types. The authentication types can be added by selecting the type from the selection menu and clicking the 'Save' button.
Authentication - Add / Delete Users
A list of users who are allowed to access the HTTP Proxy can be configured by selecting the users from the 'Available Users' list and clicking the 'Add' button. 
Note: These users can also be added by checking the checkbox against HTTP users in the 'Users"' menu of the  'User Authentication' section.
The users who currently have HTTP access can be denied access by selecting the users to be deined acces from the 'Allowed Users' list and clicking on the 'Delete' button.
The 'Allowed Users' list consists of the local users who are allowed HTTP access and the 'Availlable Users' list consists of the local users who are not allowed HTTP access.