Opened 6 years ago
Last modified 16 months ago
#42007 new defect (bug)
rpc.pingomatic.com still using HTTP
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 4.9 |
| Component: | Pings/Trackbacks | Keywords: | has-patch |
| Focuses: | administration | Cc: |
Description (last modified by )
It looks like rpc.pingomatic.com still doesn't support https. I would like to see it support HTTPS, and then have WordPress default to using https for it.
Attachments (1)
Change History (4)
This ticket was mentioned in PR #3046 on WordPress/wordpress-develop by sabernhardt.
16 months ago
#1
- Keywords has-patch added
This ticket was mentioned in PR #3046 on WordPress/wordpress-develop by sabernhardt.
16 months ago
#2
#3
@
16 months ago
- Description modified (diff)
Thanks for the report and sorry for the long delay!
The rpc.pingomatic.com subdomain still does not seem to support HTTPS, but I made a patch to update the schema for new sites if the subdomain gets SSL.
All unit tests passed with only the schema.php change. I also wanted to update the unit test to check both HTTP and HTTPS, and (only) the 7.0-multisite test failed. The failure notice mentions a timeout. (I had planned to try a pull request on my fork first. :facepalm:)
When this is completed, the Update Services support article will need updating (both the screenshot and the list).
Update Services field on Writing Settings screen