You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a response is set Content-Length header - we should not encode the body.
If there neither Content-Length header nor Transfer-Encoding: chunked - we should encode the body. Hyper can do it easily.
If there is Transfer-Encoding: chunked - we should firstly decode the body and to encode it again to avoid double-encoding.
Another issue is - there is some kind of accept logging. In the case of chunked TE it will be broken, as Hyper provides no way to notify when the last body chunk was written.
The text was updated successfully, but these errors were encountered:
This can be tricky, because:
Content-Length
header - we should not encode the body.Content-Length
header norTransfer-Encoding: chunked
- we should encode the body. Hyper can do it easily.Transfer-Encoding: chunked
- we should firstly decode the body and to encode it again to avoid double-encoding.Another issue is - there is some kind of accept logging. In the case of chunked TE it will be broken, as Hyper provides no way to notify when the last body chunk was written.
The text was updated successfully, but these errors were encountered: