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

Set appropriate headers in /services endpoint. #4596

Merged
merged 2 commits into from
Jan 21, 2022

Conversation

jmcarp
Copy link
Contributor

@jmcarp jmcarp commented Dec 22, 2021

Signed-off-by: Josh Carp [email protected]

What this PR does:

I noticed that the /services endpoint response renders as plain text in some situations. The /services endpoint also sets Content-Type to text/plain when returning json. I see that we always set the Content-type to text/plain in the handler, which I'm proposing we drop unless we need it for some reason.

Which issue(s) this PR fixes:
Fixes #

Checklist

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

Copy link
Contributor

@bboreham bboreham left a comment

Choose a reason for hiding this comment

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

Thanks!
Looks like this was an omission from #2673.
Could you reword the CHANGELOG entry so that an administrator can read through the list and get some idea whether they need this fix? It should be understandable without having to refer to the source code.
E.g. "/services html was previously declared to be plain text"

@jmcarp jmcarp force-pushed the jmcarp/services-content-type branch from ac137a3 to 28b5677 Compare December 23, 2021 16:34
@jmcarp
Copy link
Contributor Author

jmcarp commented Jan 4, 2022

Happy new year @bboreham! I fixed the changelog. Let me know if I missed anything else.

@alvinlin123
Copy link
Contributor

@jmcarp thanks for the contribution! Would you be able to fix the conflicts and I'll get this PR merges :-)

@alvinlin123 alvinlin123 enabled auto-merge (squash) January 21, 2022 05:21
@alvinlin123
Copy link
Contributor

Alright, I was afraid that if I make edit through web UI for change log DCO would complain, but looks like it didn't :-) Sorry for the false alarm @jmcarp

@alvinlin123 alvinlin123 merged commit c458295 into cortexproject:master Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants