-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support to Chunk-Encoded Requests #13
Comments
With curl (therefore with https://github.com/diepm/vim-rest-console/ )
For instance thanks Wireshark we could know that
|
Hi Julio, I'm not explicitly adding a |
If you want an example, use
You could see in the As I said in the first comment, chunked request have this problem. A chunked request should not have the It seams that you must do something like http://2.python-requests.org/en/master/user/advanced/#chunk-encoded-requests But probably it's not so important. Support Chunk-Encoded request is probably not a goal very important. Maybe nobody is interesting in this feature. |
Hi !
When we could see in
__roast_headers__
, on each request `Content-Length is automatically append in the header request.even if the roast file is like :
Note: for
GET http://google.fr
theContent-Length
header is not added.It's a big problem because if we want specify the header
Transfer-Encoding: chunked
it cause a conflict.The HTTP specification says:
"Expert Info (Warning/Malformed): The Content-Length and Transfer-Encoding header must not be set together" (message from Wireshark).
See also https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding
Maybe it could be cool to have a way to not add automatically this HEADER field.
Thanks in advance.
The text was updated successfully, but these errors were encountered: