This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
Set Host header for graphite-proxied requests to graphite host, not incoming host header #1980
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.
Due to an unresolved issue in the
net/http/httputil
package, Metrictrank can't reach a Graphite-Web fallback hosted behind an AWS application load balancer configured to route requests based on their host header.The request's
Host
attribute, sent by Metrictank and read by the application load balancer, should match the request'sURL.Host
attribute to be correctly routed.Currently, the
Host
attribute is set to the original request's host (the request made to Metrictank, which need to be proxified to Graphite).This workaround replace the request's bad
Host
attribute with the expected value stored inURL.Host
attribute.