ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A redirects to (http) redirects to . See for background on identifying this. (https) is fine.

Note there are lots of links to HTTP, such as the headline of

I guess this is related to recent host migrations

And it is bit related to Enforce HTTPS on ROS Wiki and

Highly recommended that goes through the steps to get added to the HSTS preload list. c.f. , , etc

As getting HSTS preload ready, approved and released into browsers takes a while, it would be sensible to have added to HTTPS Everywhere. Someone requested it at , but nobody stepped up to do it.

Are the ROS related entries on still accurate?

1 Like

Not sure whether this was a DNS caching issue.

Just checked this (from Europe) and with both http and https links is loaded.

We did have the site temporarily redirecting to while it was under active migration but that was removed at the same time for https as http. My best guess is that you were encountering some caching on a transparent proxy that was not correctly setup.

I added to the https ticket to look at forcing hsts too.

I’ve found four hosts failing in that list:

They don’t appear to be related to ROS, but if they are:

Have they been replaced with new hosts, or simply removed as no longer needed?

Are there new ROS related hosts on ?

We don’t host anything under the domain.

You may not, but it is hosting ROS sites/mirrors. Perhaps they were previously involved in helping ROS infrastructure - they often help large projects until they are sufficiently stable and capable of self-hosting.

The hosts are listed as errors in the XML file I linked to, but I’ll repeat the obvious ones here.

The following HTTP all redirect to the status site on

They all fail on HTTPS due to wrong cert domains. See

Other sites: - mirror error - redirects to https causing cert error - live site

For all things OSU, @wdsmart.

I’m out of the loop on the hosting…

OSUOSL is our primary hosting for several services since 2013 As part of how the machines are administered they have alternative DNS resolutions under the domain. However we do not serve the ROS content on those domains.

I don’t know why they were added to that list and would probably suggest that they not be there at all as there’s no web content available there nor is there expected to be any at any point in the future so it’s a waste of space in the https-everywhere database and people will spend time trying to update them or expecting them to work.