fix(HTTP Request Node): Respect the original encoding of the incoming response #9869
+176
−58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
n8n-assistant
bot
added
core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Almost all of our response handling code in nodes was ignoring the encoding defined on the
content-typeheader. This PR updates all of this code to respect the encoding of the original document.Before the fix:
After the fix:
PS: This does not fix the issue in v1 and v2 of the HttpRequest node. I tried, but it turned out to be too messy to be worth fixing.
Related Linear tickets, Github issues, and Community forum posts
Fixes #8799
Review / Merge checklist