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

[pull] main from remix-run:main #3

Merged
merged 2 commits into from
Feb 16, 2024
Merged

[pull] main from remix-run:main #3

merged 2 commits into from
Feb 16, 2024

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 16, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

jacob-ebey and others added 2 commits February 14, 2024 10:36
…es (#54)

When the `compress` flag is set to true, the fetch implementation sends an Accept-Encoding header and decompresses the response.

However, the decompressed body is put into a `Response` that still has a `Content-Encoding` that no longer matches the actual encoding of the body.

This causes issues if this `Response` object is used downstream (i.e. sent back to a browser), and there is another attempt to decode the body based on the content-encoding header.

Co-authored-by: Jacob Ebey <jacob.ebey@live.com>
@pull pull bot added the ⤵️ pull label Feb 16, 2024
@pull pull bot merged commit 822a3c3 into MichaelDeBoey:main Feb 16, 2024
65 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants