In this page you find:
The HTTP proxy employed in the Endian Hotspot Appliance is squid, whose primary ability is to cache web requests to speed up future requests of the same page, though it has many more functionalities that allows its seamless integration with the other services described in the remainder of this section. The HTTP proxy settings page is organized in tabs from which it is possible to configure all the options.
A click on the Enable HTTP Proxy switch enables the HTTP proxy. After some seconds, necessary to start all required services, a number of controls appear in the Configuration tab, grouped into six panels: Each panel has a title, followed by a ? that shows a tooltip, and can be expanded or collapsed by clicking on the or icons located on the left of the labels.
Completely transparent protection throught the HTTP proxy.
The HTTP proxy will work in a completely transparent way. This means that users that are connected to the Endian Hotspot Appliance‘s BLUE zone do not need to change the configuration of their devices as all the traffic will automatically go through the proxy and be scanned for viruses or filtered there in any case.
When enabling the proxy please note that it will be enabled for the BLUE WiFi zone only and the configuration will not be applied to the management network (GREEN zone). This means that filtering the content or scanning for viruses in the GREEN zone is not possible.
In the Proxy settings panel there are some global configuration options for the proxy services:
Configuration option for the ports the clients are allowed to use when browsing:
Configuration option to enable the logging facility and choosing what to log.
?id=123
)In this panel some exception to the transparent proxy can be defined, i.e., which sources (i.e., clients) and destinations (i.e., remote servers) should be ignored by the proxy, even if it is enabled in that zone.
The destinations that are not subject to the transparent proxy.
Hint
Use CIDR notation to enter subnets.
Configuration options for the space occupied on disk by the cache and the size of the objects stored.
Note
Objects whose size does not fall within the above defined ranges will never be stored on disk, but downloaded each time they are requested by some client.
When this option is enabled (i.e., the checkbox is ticked), the proxy will never try to update cached objects from the upstream web server - clients can then browse cached, static websites even after the uplink went down.
Warning
This option proves useful to surf the Internet while the uplink is down, if the page requested has been cached before. However, this option may cause some trouble when trying to refresh a page, even with a working uplink, since the HTTP proxy would always serve the cached page. The only possibility to have a refreshed copy of a web page is in this case to clear the cache of the proxy server.
If there is another proxy server in the LAN, it can be contacted before actually requesting the original resource. This panel contains configuration options for the connection between the Endian Hotspot Appliance and the upstream proxy.
The accesses policies are applied to every client that is connecting through the proxy, regardless of its authentication. An access policy rule is a time-based scheme that permits or prohibits accesses depending on diverse parameters about the user (e.g. the source or destination of the traffic), and the client used or the content downloaded (e.g., the user agent, the mime types, virus scanning, and content filtering).
A list of the already defined rules is displayed on the page. Any rule can specify if the web access is blocked or allowed, and in the latter case a filter type can be activated and selected. The table carries the following information for every rule listed therein: The progressive identification number (#), the name (``), the source and destination interested, the authentication type, if required, the periods in which is active, the user agents matched, and the available actions:
To add a new access policy rule, simply click on Add Access policy: A form will open, in which to configure all the parameters:
Select one ore more days of the week.
Hint
To select two or more days, hold the CTRL
keys
and click the mouse button on the name of the day.
A list of the MIME types of incoming files that should be blocked, one per line. MIME types can only be blocked (i.e., blacklisted) but not allowed (i.e., whitelisted), therefore this option is only available in Deny access policies. This option allows to block any files not corresponding to the company policy (e.g., multimedia files).
The available actions allow to change priority, edit, enable/disable or delete each rule from the list of rules.
The Endian Hotspot Appliance‘s content filter abilities are based on the Cyren URL filtering solution, that uses two filtering techniques which can be defined per filter profile.
The first one consists of an advanced method of web pages categorisation, based on their content, while the second method uses a combination of white- and blacklists URLs and domains: All the URLs requested by a client are looked up in this list and are only served if they are found in the whitelist.
Note
If the system has not yet been registered to Endian Network, the URL filter lists can not be downloaded. In this case, an informative message appears: By clicking on it, the registration form will open.
A profile is needed to be able to use the content filter. There is a Default profile available, which allows access to every web page and shall not be deleted. Additional profiles, that are needed in the definition of an Access policy, can easily be created. Hence, an access policies requiring a specific profile can be created only after that profile.
On the page, there is a list of the existing profiles, accompanied by a remark and by the available actions:
Above the table, there is a Create a profile link: When clicked, the link is replaced by the Profile Editor, that is used to configure a new profile, with the list of existing profiles shifting to the bottom of the page. The following settings can be defined:
In this section it is possible to enable the SafeSearch Enforcement functionality for the supported search engines. At the moment these are:
SafeSearch Enforcement
With the standard web filtering functionality it is already possible to filter inappropriate web sites for children or students. However, this does not affect results such as preview images that are coming from the search engines.
Since search engines are caching images it is impossible to know from which website they are coming and therefore they cannot be blocked based on their category. To still be able to block inappropriate or offensive content many search engines include a SafeSearch functionality that, when enabled, will simply not include these results.
When using SafeSearch Enforcement this behaviour is being enforced for the selected search engines regardless of the user’s personal settings.
Since most search engines today are automatically using HTTPS it is necessary to enable the HTTPS Proxy.
The next settings come in form of panels, that can be expanded or collapsed by clicking on the or icons to the left of their title. On the far right, a small arrow shows if the contained items are all, none, or partially allowed. Those arrows can be clicked to quickly toggle the status of all the contained items.
The categories to activate for applying the content filter. Each category contains additional sub-categories, that can be individually allowed or not. A green arrow means that the (sub-)category’s items are used for content filter, while a icon means that those items are not used. A icon near the category name shows that only some of the sub-categories within it are used for content filtering.
Here personalised lists of web pages can be added as always allowed (whitelist), i.e., they will always be served to the clients, or denied (blacklist), i.e., they will never be served to the clients.
Content filtering may cause both false positives and false negatives, hence list domains that should always be blocked or allowed can be entered here. This policy will be applied regardless of the results of the content filter’s analysis.
In this page it is possible to configure the proxy server for the scan of SSL-encrypted traffic, i.e., traffic through the 443 port. When enabled, squid will intercept all clients’ requests and forward them to the remote server, like in the case of HTTP requests. The only difference is that for HTTPS requests, an ‘intermediate’ certificate is needed for the client to connect via HTTPS to the Endian Hotspot Appliance, which then can deliver the request, retrieve the remote resource, control it, and then send it to the client who requested it.
There are three available settings in this page, divided in two parts: The first one allows the set up the HTTPS proxy, whereas the second one is used to manage the Endian Hotspot Appliance‘s certificate.
When this option is used, the HTTPS traffic will be managed directly by the upstream proxy, otherwise it is managed by the Endian Hotspot Appliance.
Note
This option only works if an upstream proxy has been defined in the upstream proxy (See ).
To activate the HTTPS proxy, click on Save and wait a few seconds.
The lower part can be used to either upload a certificate that will be used by the Endian Hotspot Appliance or to generate a new one, that will replace the one already present, if any.
After the certificate has been uploaded or created, a new option in the form of a hyperlink will appear next to the Upload proxy certificate label: