- Aligned and fixed behavior for encoding of request with respect to redirect in the two implementations
- Use only binary encoding in curl implementation for the file used to spool the body, to avoid
corruption of content (eventual encoding has already happened in its proper place)
- Allow only for curl to exploit native file POSTing capability (only way to POST files > 2GB)
TODO: wrap this behavior in the generic API
- Add content-length header when POSTing content, as some servers will require it (curl did this already)
