Opened 13 years ago
Closed 13 years ago
#17416 closed defect (bug) (fixed)
Use wp_remote_retrieve_* functions where appropriate
Reported by: | aaroncampbell | Owned by: | nacin |
---|---|---|---|
Milestone: | 3.2 | Priority: | normal |
Severity: | normal | Version: | 3.2 |
Component: | Administration | Keywords: | has-patch |
Focuses: | Cc: |
Description (last modified by )
There are quite a few places where we're not using these:
wp_remote_retrieve_headers()
wp_remote_retrieve_header()
wp_remote_retrieve_response_code()
wp_remote_retrieve_response_message()
wp_remote_retrieve_body()
.
Attachments (2)
Change History (9)
#1
@
13 years ago
- Component changed from General to Administration
- Keywords has-patch added
- Milestone changed from Awaiting Review to 3.2
- Version set to 3.2
#2
follow-up:
↓ 3
@
13 years ago
- Owner set to nacin
- Status changed from new to accepted
Figured you'd notice that :)
#4
@
13 years ago
Old habits die hard? It looks like there are other places in core where this should be done as well:
- wp-admin/includes/plugin-install.php
- wp-admin/includes/theme.php
- wp-include/class-feed.php
- wp-include/class-wp-http-ixr-client.php
- wp-include/comment.php
- wp-include/functions.php
- wp-include/rss.php
- wp-include/update.php
I'll just expand this ticket and make a new patch.
#5
@
13 years ago
- Description modified (diff)
- Keywords has-patch removed
- Summary changed from Browser nag should use built-in HTTP functions to Use wp_remote_retrieve_* functions where appropriate
Note: See
TracTickets for help on using
tickets.
Also removes useless $raw_response var