Fix proxied url hostnames and thus code-submitter urls #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
There's been a long-standing issue where the hosted code-submitter emits urls which point at the machine hosting it, leading to users ending up on that domain rather than on our root domain.
The two previously observed failure modes were:
Host
header so that nginx on the service machine is happyHost
header (so that the urls are right) but the service machine's nginx is trying to canonicalise its domainThis PR fixes the issue by:
This is approximately the same fix as was attempted in #37, however it seems that that PR didn't work due to the mismatch of types in the
secondary_hostnames
value (it's now a list, was presumably a string previously).Code review
Reviewing the changes by commit may be useful.
Testing
Links
Extra context: PeterJCLaw/code-submitter#31