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

query-tee: proxy Content-Type response header #5183

Merged
merged 2 commits into from
Jun 7, 2023

Conversation

dimitarvdimitrov
Copy link
Contributor

What this PR does

The query-tee doesn't proxy the content-type HTTP header. This breaks some integrations, such as Grafana Alerting.

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

The query-tee doesn't proxy the content-type HTTP header. This breaks some integrations, such as Grafana Alerting.

Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Signed-off-by: Dimitar Dimitrov <dimitar.dimitrov@grafana.com>
Copy link
Contributor

@charleskorn charleskorn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dimitarvdimitrov dimitarvdimitrov merged commit 053436b into main Jun 7, 2023
@dimitarvdimitrov dimitarvdimitrov deleted the dimitar/query-tee/propagate-content-type branch June 7, 2023 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants