WordPress / WordPress/Requests
Requests_Exception with message 'cURL error 18: transfer closed with 1 bytes remaining to read'
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 500
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 5
Description
The stackoverflow says that I might be able to work around this by forcing HTTP1.0
Assuming this error is the server's fault, I'm not sure how to do this via Requests:
curl_setopt($curl, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_0);
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Requests' cURL option handling around the HTTP version setting referenced in the issue and compare it with CURLOPT_HTTP_VERSION. Done means the reported request can be forced to HTTP/1.0, with the behavior verified against the cURL error described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100