fix: revert doc deletion, revert test_helper change, refs #4339
This commit is contained in:
@@ -143,6 +143,12 @@ dokku nginx:set node-js-app trust-x-forwarded-for true
|
|||||||
dokku nginx:set node-js-app trust-x-forwarded-for false
|
dokku nginx:set node-js-app trust-x-forwarded-for false
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Only use this option if:
|
||||||
|
1. All requests are terminated at the load balancer, and forwarded to Nginx
|
||||||
|
2. The load balancer is configured to send the `X-Forwarded-` headers (this may be off by default)
|
||||||
|
|
||||||
|
If it's possible to make HTTP(S) requests directly to Nginx, bypassing the load balancer, or if the load balancer is not configured to set these headers, then it becomes possible for a client to set these headers to arbitrary values.
|
||||||
|
|
||||||
### SSL Port Exposure
|
### SSL Port Exposure
|
||||||
|
|
||||||
When your app is served from port `80` then the `/home/dokku/APP/nginx.conf` file will automatically be updated to instruct nginx to respond to ssl on port 443 as a new cert is added. If your app uses a non-standard port (perhaps you have a dockerfile deploy exposing port `99999`) you may need to manually expose an ssl port via `dokku proxy:ports-add <APP> https:443:99999`.
|
When your app is served from port `80` then the `/home/dokku/APP/nginx.conf` file will automatically be updated to instruct nginx to respond to ssl on port 443 as a new cert is added. If your app uses a non-standard port (perhaps you have a dockerfile deploy exposing port `99999`) you may need to manually expose an ssl port via `dokku proxy:ports-add <APP> https:443:99999`.
|
||||||
|
|||||||
@@ -406,7 +406,7 @@ server {
|
|||||||
proxy_set_header Connection \$http_connection;
|
proxy_set_header Connection \$http_connection;
|
||||||
proxy_set_header Host \$http_host;
|
proxy_set_header Host \$http_host;
|
||||||
proxy_set_header X-Forwarded-Proto \$scheme;
|
proxy_set_header X-Forwarded-Proto \$scheme;
|
||||||
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
|
proxy_set_header X-Forwarded-For \$remote_addr;
|
||||||
proxy_set_header X-Forwarded-Port \$server_port;
|
proxy_set_header X-Forwarded-Port \$server_port;
|
||||||
proxy_set_header X-Request-Start \$msec;
|
proxy_set_header X-Request-Start \$msec;
|
||||||
}
|
}
|
||||||
@@ -453,7 +453,7 @@ server {
|
|||||||
proxy_set_header Connection "upgrade";
|
proxy_set_header Connection "upgrade";
|
||||||
proxy_set_header Host \$http_host;
|
proxy_set_header Host \$http_host;
|
||||||
proxy_set_header X-Forwarded-Proto \$scheme;
|
proxy_set_header X-Forwarded-Proto \$scheme;
|
||||||
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
|
proxy_set_header X-Forwarded-For \$remote_addr;
|
||||||
proxy_set_header X-Forwarded-Port \$server_port;
|
proxy_set_header X-Forwarded-Port \$server_port;
|
||||||
proxy_set_header X-Request-Start \$msec;
|
proxy_set_header X-Request-Start \$msec;
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user