Opened 9 years ago
Closed 9 years ago
#33529 closed defect (bug) (wontfix)
IXR_Client overrides and sets incorrect HTTPS default port
Reported by: | beaucollins | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | XML-RPC | Keywords: | close |
Focuses: | Cc: |
Description
IXR_Client will attempt to parse the correct parameters from the $server argument when $path is not provided.
In cases where the port is not provided within the url (e.g. "https://example.com:443/") it will always default to port 80 no matter which scheme is used.
If no port is in the URL it should default to the correct port for the given scheme.
Attachments (1)
Change History (4)
Note: See
TracTickets for help on using
tickets.
Realistically clients should be extending
WP_HTTP_IXR_Client
instead - it uses the HTTP API rather than directfsockopen
calls, and doesn't suffer from this problem.