|
|
@@ -5,7 +5,7 @@
|
|
|
This is a list of valid fully-qualified domain names (FQDNs) and/or IP addresses that can be used to reach the NetBox service. Usually this is the same as the hostname for the NetBox server, but can also be different; for example, when using a reverse proxy serving the NetBox website under a different FQDN than the hostname of the NetBox server. To help guard against [HTTP Host header attackes](https://docs.djangoproject.com/en/3.0/topics/security/#host-headers-virtual-hosting), NetBox will not permit access to the server via any other hostnames (or IPs).
|
|
|
|
|
|
!!! note
|
|
|
- This parameter must always be defined as a list or tuple, even if only value is provided.
|
|
|
+ This parameter must always be defined as a list or tuple, even if only a single value is provided.
|
|
|
|
|
|
The value of this option is also used to set `CSRF_TRUSTED_ORIGINS`, which restricts POST requests to the same set of hosts (more about this [here](https://docs.djangoproject.com/en/stable/ref/settings/#std:setting-CSRF_TRUSTED_ORIGINS)). Keep in mind that NetBox, by default, sets `USE_X_FORWARDED_HOST` to true, which means that if you're using a reverse proxy, it's the FQDN used to reach that reverse proxy which needs to be in this list (more about this [here](https://docs.djangoproject.com/en/stable/ref/settings/#allowed-hosts)).
|
|
|
|
|
|
@@ -101,7 +101,7 @@ REDIS = {
|
|
|
|
|
|
If you are using [Redis Sentinel](https://redis.io/topics/sentinel) for high-availability purposes, there is minimal
|
|
|
configuration necessary to convert NetBox to recognize it. It requires the removal of the `HOST` and `PORT` keys from
|
|
|
-above and the addition of two new keys.
|
|
|
+above and the addition of three new keys.
|
|
|
|
|
|
* `SENTINELS`: List of tuples or tuple of tuples with each inner tuple containing the name or IP address
|
|
|
of the Redis server and port for each sentinel instance to connect to
|
Jeremy Stretch