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
undici - next #2835
Comments
With |
It's methods on |
Some of the above we can probably land on main. |
This seems interesting, in theory, the HTTP response is split into three parts, the status line, headers and body; maybe we can follow this line? |
it's actually headers first, then status and then body. |
I'm working on the dump to interceptor, but I'm curious what do you have in mind for that API? Also removing the legacy interceptor concepts from |
cc: @ronag |
I will sort the next branch sometime in the next two weeks. Just open or against current state. |
Something like that? |
It is also necessary to move the decompression of compressed data (gzip, deflate, br, zstd) into a separate interceptor |
TODO:
throwOnError
to interceptorReadable.setEncoding
issue (client.request throws Error with setEncoding #1125 (comment))[x] non-keep alive connections are not data safe[ ] Should we splitonHeaders
into more fine-grained hooks? i.e.onHeader(key, val)
andonStatus(code, message)
?Refs: #2722
The text was updated successfully, but these errors were encountered: