Skip to content

Fix content type might not be in headers #89

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.

Sign up for GitHub

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

Jump to bottom
Merged
maingoh merged 3 commits into from
Mar 30, 2020
Merged

Fix content type might not be in headers #89

maingoh merged 3 commits into from
Mar 30, 2020

Conversation

@maingoh
Copy link
Contributor

@maingoh maingoh commented Mar 30, 2020

It raised a KeyError if content-type was not in the headers and wasn't returning the response content

@maingoh maingoh requested a review from ibreschi March 30, 2020 13:15
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 30, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@maingoh maingoh merged commit f479724 into master Mar 30, 2020
@maingoh maingoh deleted the fix-content-type-response branch March 30, 2020 14:36
@maingoh maingoh mentioned this pull request Jan 11, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ibreschi ibreschi ibreschi approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@maingoh @ibreschi