#37992 closed defect (bug) (fixed)
fsockopen hard codes port 443 when http scheme used
Reported by: | amandato | Owned by: | rmccue |
---|---|---|---|
Milestone: | 4.7.1 | Priority: | normal |
Severity: | normal | Version: | 4.6.1 |
Component: | HTTP API | Keywords: | |
Focuses: | Cc: |
Description
The Transport/fsockopen.php library hard codes port 443 when the scheme https is used. This does not allow for a custom port when using the https scheme. e.g. https://example.com:900/ would be converted to https://example.com:443/. Attached patch fixes this by checking if the port is not already specified.
This patch can be applied separately but was discovered while creating the patch for ticket #37991 https://core.trac.wordpress.org/attachment/ticket/37991/. Both tickets should be addressed together as they are related (this one impacts #37991 and #37991 restores expected behavior for https scheme).
Attachments (1)
Change History (8)
#1
@
8 years ago
- Component changed from General to HTTP API
- Owner set to dd32
- Status changed from new to accepted
#4
@
8 years ago
- Milestone changed from Awaiting Review to 4.7
- Owner changed from dd32 to rmccue
- Status changed from accepted to assigned
PR merged; needs update in core.
Note: See
TracTickets for help on using
tickets.
Hi @amandato and welcome to Trac.
Thanks for reporting this, In WordPress 4.6 we're using the external package Requests and issues/patches such as these need to be made against that upstream package.
I'll take a look into this and open a PR upstream.