Opened 11 years ago
Closed 11 years ago
#31172 closed defect (bug) (fixed)
WP_HTTP_Curl handler fails with limit_response_size when response is larger than specified
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 4.2 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | HTTP API | Keywords: | |
| Focuses: | Cc: |
Description
It appears that at present the limit_response_size parameter is broken for the cURL transport when it's not streaming the contents to a file (See #26726 for streaming to file).
It turns out that this isn't covered by any existing Unit Tests.
This was noticed by the WordPress.com team when pingbacks from documents over 150KB were failing, tracing back to WP_HTTP returning a WP_Error when limit_response_size bytes were recieved.
Change History (1)
Note: See
TracTickets for help on using
tickets.
In 31290: