Clarification needed re: Chunked Transfer Encoding
Asked by
Bob
Hi,
Re: 3.3.2.1. Chunked Transfer Encoding
The docs say :
Users can upload data without needing to know in advance the amount of data to be uploaded. Users can do this by specifying an HTTP header of Transfer-Encoding: chunked and not using a Content-Length header
Could someone please clarify the wording :
(1) Does this mean it is illegal syntax to supply a "Content-Length" header when using chunked encoding ? Or does it only mean that the "Content-Length" header is optional when using chunked encoding, and hence if I *DO* know the content-length, I can provide it, and the API will use it ?
(2) Similar question in relation to provision of Etag MD5 hash.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Bob
- Solved:
- Last query:
- Last reply:
To post a message you must log in.