Force HTTPS on gitlab.io?
Unless there's a good reason to not do this, why not serve all gitlab.io traffic as HTTPS only, and redirect any HTTP URLs?
Do not update/delete: Banner broadcast message test data
Do not update/delete: Notification broadcast message test data
Unless there's a good reason to not do this, why not serve all gitlab.io traffic as HTTPS only, and redirect any HTTP URLs?
I don't think we can do this just for gitlab.io - !21 (merged) has fixed the command-line flag, but it applies to every domain on the Pages instance, not just the default domain.
closed