For #154 I had success by preventing the recorder proxy from employing chunked Transfer-Encoding. It seemed like connect et. al just don't do well when given properly formed chunked requests.
Here's someone driving libcurl with PHP who had a similar issue: https://github.com/php/php-src/issues/8165
Based on the age of that, I wonder if cURL going to chunked Transfer-Encoding when it is uploading from CURLOPT_READFUNCTION and the length hasn't been provided ahead of time is a newer behavior.
Disclaimer: I don't really write much R :upside_down_face:
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
Mike Baynton seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it.
For #154 I had success by preventing the recorder proxy from employing chunked Transfer-Encoding. It seemed like connect et. al just don't do well when given properly formed chunked requests.
Here's someone driving libcurl with PHP who had a similar issue: https://github.com/php/php-src/issues/8165 Based on the age of that, I wonder if cURL going to chunked Transfer-Encoding when it is uploading from
CURLOPT_READFUNCTION
and the length hasn't been provided ahead of time is a newer behavior.Disclaimer: I don't really write much R :upside_down_face: