It is not possible to send pre-chunked stream

[fafhrd91]

Client code automatically enables chunking if headers contains transfer-encoding: chunked
So it is not possible to implement custom chunking encoding or send pre-chunked stream

[fafhrd91]

If chunked enabled, content-length and transfer-encoding in headers should be forbidden

[fafhrd91]

@asvetlov @kxepal

[kxepal]

@fafhrd91
Ok with content-length - IIRC spec explicitly forbids that, but isn't chunked=True in arguments and transfer-encoding: chunked in headers are synonyms? Or I miss something?

[fafhrd91]

If transfer-encoding is in headers we turn on chunking, and enable chunking on writer. But what if I want to chunk stream myself?

For content length we should raise exception if user pass it in headers and enables chunking

[fafhrd91]

also we have to honor CONTENT-LENGTH header

[fafhrd91]

fixed in 2.0

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.