| 13.3. HTTP Server configuration | ||
|---|---|---|
 | Chapter 13. System Services |  |
| 13.3. HTTP Server configuration | ||
|---|---|---|
| | Chapter 13. System Services | |
The HTTP server's purpose is to serve the HTML and supporting files that implement the web-based user-interface for the FB2500. It is not a general-purpose web server that can be used to serve user documents, and so there is little to configure.
By default, the FB2500 will allow access to the user interface from any machine, although obviously access to the user interface normally requires the correct login credentials to be provided. However, if you have no need for your FB2500 to be accessed from arbitrary machines, then you may wish to 'lock-down' access to the user interface to one or more client machines, thus removing an 'attack vector'.
Access can be restricted using allow and local-only controls as with any service.
If this allows access, then a user can try and login. However, access can also be restricted on a per user basis to IP addresses and using profiles, which block the login even if the passord is correct.
Additionally, access to the HTTP server can be completely restricted (to all clients) under the control of a profile. This can be used, for example, to allow access only during certain time periods.
Trusted addresses are those from which additional access to certain functions is available. They are specified by setting the
trusted attribute using address ranges or IP address group names.
This trusted access allows visibility of graphs without the need for a password, and is mandatory for packet dump access.
| |  | |
| 13.2. Common settings |  | 13.4. Telnet Server configuration |