Opened 10 years ago
Last modified 5 years ago
#31076 new defect (bug)
Multisite signup functions don't support SSL
Reported by: | SergeyBiryukov | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Login and Registration | Keywords: | needs-patch https |
Focuses: | multisite | Cc: |
Description
confirm_blog_signup(), confirm_another_blog_signup(), and wpmu_signup_blog_notification() use hardcoded http://
links.
Attachments (2)
Change History (8)
#4
@
8 years ago
In [34790], a $blog_id
parameter has been introduced in confirm_another_blog_signup()
. If it is set, then the function uses home_url()
and wp_login_url()
to generate the necessary URLs.
We could do the same thing in wpmu_signup_blog_notification()
and confirm_blog_signup()
.
This ticket was mentioned in Slack in #core-http by johnbillion. View the logs.
8 years ago
Note: See
TracTickets for help on using
tickets.
We probably need to check a little further before assuming SSL in some cases. If a new subdomain or domain is being created, it's not necessarily the case that SSL will be available for activation. For subdirectories, we should have no trouble assuming the same scheme as the network.