From 95cea427a7eef1b270403dd3d895f054450e5bea Mon Sep 17 00:00:00 2001 From: dgtlmoon Date: Thu, 9 Mar 2023 19:45:03 +0100 Subject: [PATCH] Updated Running changedetection.io behind a reverse proxy (markdown) --- Running-changedetection.io-behind-a-reverse-proxy.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/Running-changedetection.io-behind-a-reverse-proxy.md b/Running-changedetection.io-behind-a-reverse-proxy.md index 98efb41..3506b41 100644 --- a/Running-changedetection.io-behind-a-reverse-proxy.md +++ b/Running-changedetection.io-behind-a-reverse-proxy.md @@ -1,6 +1,3 @@ -Before moving on, if your endpoint looks like this: `https://domain.com/subdirectory_dedicated_to_changedetector` -Please review [this article](https://github.com/dgtlmoon/changedetection.io/wiki/Running-changedetection.io-behind-a-reverse-proxy-sub-directory) then come back here - You need to enable the `USE_X_SETTINGS` environment variable in changedetection.io for it to respect HTTP headers sent from the reverse proxy (such as `Host`, `X-Forwarded-Prefix` and `X-Forwarded-Proto`). The easiest way is to create an extra docker-compose YML file and run it with the shipped version.