Security |
On the tab, you can configure restrictions for network addresses from which the Web server receives HTTP and HTTPS requests. General •Set the flag to automatically redirect all HTTP connections to HTTPS. •Set the flag to return environment details in the “Server” header by the web server. •Set the flag to convert all URI in requests to the web server to lowercase. Only a fragment of URI hierarchical part that contains path is converted. •Set the flag to forbid the access to the Control Center interface for bots and other User Agents from the list below. Define the list of forbidden User Agents: ▫In the field specify User Agent name to forbid the access to the Control Center interface. Case sensitive. If not set, the application URI is used. ▫In the field, specify regular expression defining the application to forbid the access to the Control Center interface. Access Restiction To setup access limitations for any of connection type 1.To allow the access by HTTP or by HTTPS from definite addresses, add them to the or lists correspondingly. 2.To deny the access by HTTP or by HTTPS from definite addresses, add them to the or lists correspondingly. 3.The addresses not included into any of the lists are allowed or denied depending on whether the and flags are set: if the flag is set, the addresses not included into any of the lists (or included into both of them) are denied. Otherwise, such addresses are allowed. To edit the address list 1.Specify the network address in the corresponding field and click . 2.The network address is specified as: <IP-address>/[<prefix>].
3.To add a new field, click in the corresponding section. 4.To delete a field, click . Examples of prefix usage: 1.Prefix 24 stands for a network with a network mask: 255.255.255.0 Containing 254 addresses. Host addresses look like: 195.136.12.* 2.Prefix 8 stands for a network with a network mask: 255.0.0.0 Containing up to 16777214 addresses (256*256*256-2). Host addresses look like: 125.*.*.* |