Opened 16 years ago
Closed 16 years ago
#7793 closed enhancement (fixed)
Transition all fsockopen, fopen, and curl to HTTP API
Reported by: | jacobsantos | Owned by: | jacobsantos |
---|---|---|---|
Milestone: | 2.7 | Priority: | normal |
Severity: | normal | Version: | 2.7 |
Component: | Optimization | Keywords: | http has-patch commit |
Focuses: | Cc: |
Description
Ticket is for transitioning the remaining functions over to the HTTP API. This does not include the dependencies on Snoopy, but it might in the future. It also does not include the SSL remote URL check, I'm not sure how to achieve that using the API (look for 200 maybe and check that URL was not redirected, maybe).
Supercedes #7224, #7676, and #7751.
Discussion on removing Snoopy can also begin. I'll start, basically since Magpie requires it, it might be best to leave it alone. The core of WordPress now doesn't use it (I'll confirm that), so it might not make sense refactoring an external library to use a WordPress one.
Attachments (3)
Change History (20)
#7
@
16 years ago
- Version set to 2.7
attachment 7793.diff added.
converts download_url() from snoopy to the new HTTP API
#9
@
16 years ago
download_url() now fails for me. It returns a 0 length file when downloading the nightly build. Get transport is curl. Post transport is streams.
#10
@
16 years ago
Response is:
array(3) { ["headers"]=> array(0) { } ["body"]=> string(0) "" ["response"]=> array(2) { ["code"]=> int(200) ["message"]=> string(2) "OK" } }
#11
@
16 years ago
sounds like you might have a problem with the curl transport, as its working for me with the HTTP Extension. I'll have a look at if i get a chance today
#12
@
16 years ago
curl_error() says:
Operation timed out after 3000 milliseconds with 1350984 out of 1815410 bytes received
HTTP API transition based on r8984