Opened 15 years ago
Closed 15 years ago
#17416 closed defect (bug) (fixed)
Use wp_remote_retrieve_* functions where appropriate
| Reported by: | aaroncampbell | Owned by: | nacin |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.2 |
| Component: | Administration | Version: | 3.2 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
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
@
15 years ago
- Component General → Administration
- Keywords has-patch added
- Milestone Awaiting Review → 3.2
- Version → 3.2
#4
@
15 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
@
15 years ago
- Description modified (diff)
- Keywords has-patch removed
- Summary Browser nag should use built-in HTTP functions → Use wp_remote_retrieve_* functions where appropriate
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Also removes useless $raw_response var