fix(docs): clarify proxy fix usage with reverse proxies
Added additional context to the explanation of the ProxyFix middleware in the README. It now details how to recognize issues with the `X-Forwarded-Host` header, such as the URL displaying internal IP and port instead of the domain name. This improvement helps users better understand when to enable the `PROXY_FIX` environment variable.
This commit is contained in:
parent
c67746ea89
commit
907df9dc1f
1 changed files with 1 additions and 1 deletions
|
@ -107,7 +107,7 @@ This is a basic guide to deploy Small using uWSGI and Caddy.
|
||||||
|
|
||||||
#### Proxy Fix
|
#### Proxy Fix
|
||||||
|
|
||||||
If you are using a reverse proxy like Nginx, and it is setting the `X-Forwarded-Host` header instead of passing the `Host` header, you can use the `ProxyFix` middleware to fix the issue. To enable it, simply set the `PROXY_FIX` environment variable to `1`.
|
If you are using a reverse proxy like Nginx, and it is setting the `X-Forwarded-Host` header instead of passing the `Host` header (you will notice this if the URL displayed on the landing page shows the internal IP and port instead of the domain name), you can use the `ProxyFix` middleware to fix the issue. To enable it, simply set the `PROXY_FIX` environment variable to `1`.
|
||||||
|
|
||||||
For uWSGI, you can add the following line to the `small.ini` file:
|
For uWSGI, you can add the following line to the `small.ini` file:
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in a new issue