mirror of
https://github.com/zulip/zulip.git
synced 2026-06-30 21:11:04 +08:00
3ec896ebda
In some cases, it is not possible to configure the load-balancer to add an X-Forwarded-Proto header. If Zulip is serving its traffic over HTTP, it will rightly error out, since it cannot guarantee that its response will be served over an encrypted connection. Add a new `loadbalancer.rejects_http_requests` settings which serves as a way for the operator to swear that the load-balancer will *never* serve responses from Zulip over an unencrypted connection. In most cases, this is because the load-balancer is configured to have port 80 always serve an HTTP 301 redirect to the same URL over HTTPS. Properly configuring the proxy to send `X-Forwarded-Proto` is always a better solution than using this configuration parameter, so use of this should be viewed as a last resort. |
||
|---|---|---|
| .. | ||
| authentication-methods.md | ||
| deployment.md | ||
| email-gateway.md | ||
| email.md | ||
| export-and-import.md | ||
| giphy-gif-integration.md | ||
| index.md | ||
| install-existing-server.md | ||
| install.md | ||
| maintain-secure-upgrade.md | ||
| management-commands.md | ||
| mobile-push-notifications.md | ||
| modify.md | ||
| multiple-organizations.md | ||
| password-strength.md | ||
| postgresql-support-table.md | ||
| postgresql.md | ||
| requirements.md | ||
| reverse-proxies.md | ||
| scim.md | ||
| security-model.md | ||
| settings.md | ||
| ssl-certificates.md | ||
| system-configuration.md | ||
| troubleshooting.md | ||
| upgrade.md | ||
| upload-backends.md | ||
| video-calls.md | ||