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

next-edge proxy dont work with new zstd encoding #70

Open
afreakk opened this issue Nov 11, 2024 · 2 comments
Open

next-edge proxy dont work with new zstd encoding #70

afreakk opened this issue Nov 11, 2024 · 2 comments

Comments

@afreakk
Copy link
Contributor

afreakk commented Nov 11, 2024

When using newer chrome, it now has zstd encoding. and when that is being utilized it result in the following response.
image
A workaround currently is

req.headers['accept-encoding'] = req.headers['accept-encoding']
            .split(', ')
            .filter((enc) => enc != 'zstd')
            .join(', ');
@aeneasr
Copy link
Member

aeneasr commented Nov 12, 2024

Would you be open to open a PR for this? :)

@afreakk
Copy link
Contributor Author

afreakk commented Nov 20, 2024

You mean fixing it properly, or just disabling zstd encoding like the thing above?
I also need this fixed #68
Right now im using a fork of this that has these changes, otherwise it wouldnt work at all with selfservice-ui-node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants