Skip to content

fix: strip content-encoding headers in proxy #10

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

Merged
worlddriven merged 1 commit into from
Feb 15, 2026
Merged

fix: strip content-encoding headers in proxy #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions server/proxy.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,9 +71,18 @@ async function handleProxy(req, res) {
}
console.log(`[Proxy] Response status: ${response.status}`);

// Copy response headers (excluding set-cookie which we handle separately)
// Copy response headers, excluding:
// - set-cookie: handled separately for auth
// - content-encoding: fetch() auto-decompresses, so body is already plain
// - content-length: no longer accurate after decompression
const skipHeaders = new Set([
'set-cookie',
'content-encoding',
'content-length',
'transfer-encoding',
]);
response.headers.forEach((value, key) => {
if (key.toLowerCase() !== 'set-cookie') {
if (!skipHeaders.has(key.toLowerCase())) {
res.setHeader(key, value);
}
});
Expand Down