diff options
| author | Markus Heiser <markus.heiser@darmarIT.de> | 2025-08-10 11:08:57 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-10 11:08:57 +0200 |
| commit | a0dd416e8a4ff6365df042474c34ace4243a1467 (patch) | |
| tree | b6b5a78e1e42dd6b80c0fd9d3c8608160f2f1e21 /utils/templates/etc/httpd/sites-available/searxng.conf | |
| parent | 935f3fe332551482d6c8a3d5b690f12d5ad67e90 (diff) | |
[fix] use X-Forwarded-Proto header if the URL scheme is unknown (#5106)
The HTTP X-Forwarded-Proto (XFP) request header is a de-facto standard header
for identifying the protocol (HTTP or HTTPS) that a client used to connect to a
proxy or load balancer.[1]
In our documentation[2] we recommend to set the `X-Scheme` header. This header
is not required if the `server.base_url` is set correctly.[3]
If none of these URL scheme details exist, then the header X-Forwarded-Proto is
evaluated as a third alternative.
[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Forwarded-Proto
[2] https://docs.searxng.org/admin/installation-apache.html#apache-s-searxng-site
[3] https://docs.searxng.org/admin/settings/settings_server.html
Closes: https://github.com/searxng/searxng/issues/5105
Diffstat (limited to 'utils/templates/etc/httpd/sites-available/searxng.conf')
0 files changed, 0 insertions, 0 deletions