Multisite new site default protocol

[kpetrilli]

Newly created sites in a multisite installation default to HTTP even though the main site is HTTPS.

Reproducible by doing the following:

• Installing WordPress, served by nginx;
• First (main) site initially set to use HTTP only
• Enable multisite (subdomain)
• Migrate everything (wp-config.php, database entries) to HTTPS only
• Create a new site

Expected behavior:

New sites should be created with HTTPS instead of HTTP.

Issues

When served by nginx, with 80 to 443 redirection (301 Moved permanently), page editor will not work, while dashboard will, on the newly created site. The redirection for the API will not work, reporting "offline" error when trying to save.

Workaround:

After the creation of the website:

1. Manually change the site's URL to use HTTPS;
2. Manually change all database entries containing http:// into https:// with a plugin such as better search replace.

Notes

I could not find how to set WordPress' default multisite protocol for new websites. I would happily avoid installing new plugins for that only.

[SergeyBiryukov]

Hi there, welcome back to WordPress Trac! Thanks for the report.

This has already been discussed in #27499. I don't think anything has really changed from that decision.

There is room for a filter to more easily allow https default, but we can continue that discussion on the other ticket.