Skip to content
This repository has been archived by the owner on Nov 26, 2024. It is now read-only.

Disregard charset in Content-Type when parsing response #631

Merged
merged 3 commits into from
Oct 27, 2023

Conversation

flowertwig
Copy link
Contributor

Disregard charset in Content-Type when parsing response, to avoid unnecessary logging if it differs from the default application/json or the Produces annotation on the resource method.

…ecessary logging if it differs from the default application/json or the Produces annotation on the resource method.
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

87.0% 87.0% Coverage
0.0% 0.0% Duplication

@jepp3
Copy link
Member

jepp3 commented Oct 27, 2023

I guess we do not specify charset in our responses from RW and that this occurs when talking with external apis, that define charset in the response?

@flowertwig
Copy link
Contributor Author

@jepp3, correct!

@flowertwig flowertwig merged commit fb95475 into master Oct 27, 2023
2 checks passed
@flowertwig flowertwig deleted the content-type-charset branch October 27, 2023 12:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants