-
Notifications
You must be signed in to change notification settings - Fork 529
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
Setting pseudo-headers for H2 request #2307
Comments
We already attach the Line 1691 in 5e654f3
As we do not support Would you like to send a PR? 🙂 |
@metcoder95 Oh, thank you for pointing me at this part of the code (I was looking at |
Feel free to open a PR for changing the order 👍 By spec, the order of the headers should not be a problem; as is not specified. But it can be obvious that some prefer a given order. |
In this case this seems like misbehavior of CloudFlare. I'm in favor of a PR that changes the order, but in parallel is there a way to influence CloudFlare and bring this to their attention? |
Not really sure, maybe you can open a thread on its community forum and seek of more consensus and maybe grasp is attention: https://community.cloudflare.com/ |
Closed by #2308 |
Bug Description
I want to use
undici
with theallowH2
flag to overcome CloudFlare anti-DDoS behavior, this requires:method
,:authority
,:path
, and:scheme
pseudo-headers to be sent, butundici
doesn't add them on its own (as browser does) and doesn't allow to set them by myself, since the header key validation from http1.1 is applied.Reproducible By
Expected Behavior
The pseudo-headers are added by the
fetch
itself, or it is possible to pass them manually.Environment
macOS Ventura 13.4.1, Node v20.5.0
The text was updated successfully, but these errors were encountered: