Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: set the Host header on the upstream block #900

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

Supermathie
Copy link
Member

Using e.g. proxy_pass http://discourse resets the Host header on the upstream
request to discourse.

This would break multisites, so we don't want that; the most effetive way to
ensure it's set properly is to set_header in the upstream block.

Using e.g. `proxy_pass http://discourse` resets the Host header on the upstream
request to `discourse`.

This would break multisites, so we don't want that; the most effetive way to
ensure it's set properly is to `set_header` in the upstream block.
Supermathie added a commit to discourse/discourse that referenced this pull request Dec 19, 2024
Using e.g. `proxy_pass http://discourse` resets the Host header on the upstream
request to `discourse`.

This would break multisites, so we don't want that; the most effetive way to
ensure it's set properly is to `set_header` in the upstream block.

See also: discourse/discourse_docker#900
Supermathie added a commit to discourse/discourse that referenced this pull request Dec 19, 2024
Using e.g. `proxy_pass http://discourse` resets the Host header on the upstream
request to `discourse`.

This would break multisites, so we don't want that; the most effetive way to
ensure it's set properly is to `set_header` in the upstream block.

See also: discourse/discourse_docker#900
@Supermathie Supermathie merged commit d8a363b into main Dec 19, 2024
5 checks passed
@Supermathie Supermathie deleted the set_host_on_upstream branch December 19, 2024 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants