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

Jump to bottom

Allow user provided connection header #1307

Open

ronag opened this issue Mar 28, 2022 · 1 comment

Labels

Member

ronag commented Mar 28, 2022

Override the pipelining option accordingly in case user passes a valid connection header.

Refs: #1305

ronag added the enhancement label

ronag mentioned this issue

Can't remove default headers. Can't overwrite "sec-fetch-mode", "connection" headers. #1305

Open

Member

metcoder95 commented May 16, 2022

Just to recap out of the discussion of #1305

The goal should be:

Allow pass custom connection-header so no error is thrown when someone wants to override the default one
Disable pipelining in case custom header is passed

Is correct, please let me know if I'm missing something 🙂

3x071c mentioned this issue

Node 18 utility for filter out blocklisted request headers trpc/trpc#2084

Closed

Kikobeats mentioned this issue

refactor: allow server-side headers #1649

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment