Skip to content

[Bug / Feature]: Charset in response headers are not considered while decoding the response text  #22078

Closed
Closed
[Bug / Feature]: Charset in response headers are not considered while decoding the response text #22078
Assignees
balachandarsv
Labels
BackendThis marks the issue or pull request to reference server codeBugSomething isn't workingCommunity ContributorMeant to track issues that are assigned to external contributorsCommunity Reportedissues reported by community membersIntegrations ProductIssues related to a specific integrationNeeds TriagingNeeds attention from maintainers to triageQuery & JS PodIssues related to the query & JS PodREST API pluginREST API plugin related issues
@balachandarsv

Description

@balachandarsv
balachandarsv
opened on Apr 4, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Description

The response contents are always read in UTF-8 charset. Sometimes the response might be in some other charsets which are not considered while decoding the response.

Steps To Reproduce

Try an API which sends the response in UTF-16

Public Sample App

No response

Environment

Production

Issue video log

No response

Version

1.16

Metadata

Metadata

Assignees

Labels

BackendThis marks the issue or pull request to reference server codeBugSomething isn't workingCommunity ContributorMeant to track issues that are assigned to external contributorsCommunity Reportedissues reported by community membersIntegrations ProductIssues related to a specific integrationNeeds TriagingNeeds attention from maintainers to triageQuery & JS PodIssues related to the query & JS PodREST API pluginREST API plugin related issues

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions