Currently, MultipartFormUpload uses PostRequestEncoder which includes transfer-encoding headers which are illegal in HTTP2 and HTTP3 as per the RFC.
Currently it is a simple fix, maybe this should be improved from the netty side itself to prevent needing to rewrite/polyfill the entire PostRequestEncoder just for such a small thing.
Fixes #2283
Side note: When testing, I noticed that the MultipartFormUpload does not report any exceptions. If theres a failure in any of the handlers, the context is unaware. Is that intentional?
Motivation:
Currently,
MultipartFormUpload
usesPostRequestEncoder
which includestransfer-encoding
headers which are illegal in HTTP2 and HTTP3 as per the RFC.Currently it is a simple fix, maybe this should be improved from the
netty
side itself to prevent needing to rewrite/polyfill the entirePostRequestEncoder
just for such a small thing.Fixes #2283
Side note: When testing, I noticed that the
MultipartFormUpload
does not report any exceptions. If theres a failure in any of the handlers, the context is unaware. Is that intentional?