Redirect planet.openstreetmap.org to HTTPS

[pnorman]

I'm splitting this out from #190 to have a dedicated issue to point to and post information specific to planet.osm.org, which has complications other subdomains don't.

The plan is to switch planet.openstreetmap.org from HTTP or HTTPS to HTTPS by default, by redirecting everything to HTTPS. During testing of this, it was identified that many clients of planet.openstreetmap.org don't follow redirects and were using http://planet.openstreetmap.org, causing their updates to fail.

The biggest issue is probably osmosis. https://trac.openstreetmap.org/ticket/5483 tracks the changes needed there. Fortunately, people can fix the problem on their install by adjusting the configuration.txt and don't need to update osmosis versions.

Steps that need doing are

• Write an email informing people of the change (@pnorman)
• Change the configuration.txt generated by osmosis --rrii (https://trac.openstreetmap.org/ticket/5483)
• Optional: Make osmosis follow redirects
• Optional: Search for configurations that need changing on code hosting sites and submit patches
• Blog post?

[SomeoneElseOSM]

For those that go that route, https://switch2osm.org/manually-building-a-tile-server-16-04-2-lts/ uses https://github.com/SomeoneElseOSM/mod_tile/tree/switch2osm (which is already customised for easier setup) and https://github.com/SomeoneElseOSM/mod_tile/blob/switch2osm/openstreetmap-tiles-update-expire changes an osmosis-initialised "http" to "https".

[grischard]

curl also doesn't follow redirects by default.

A github search finds 130 results for curl and 124 for osmosis. I can open issues like this one where relevant, but it would be great to have a sunset date. May 7?

[tomhughes]

Works for me.

[grischard]

Done tasks 1 and 4.

[grischard]

Afaict 2 is done too.

[grischard]

Of course this applies to http://planet.osm.org too.

[grischard]

So I think we can close this!

[mmd-osm]

Apologies for hijacking this closed issue. Is there an easy way to find out how many clients (in %) are currently affected by this change, i.e. they still request data from http and don't follow redirects to https?

Someone posted a munin chart to https://munin.openstreetmap.org/openstreetmap/ironbelly.openstreetmap/apache_accesses.html as a rough indication. For sure, there's some drop off at the time when the switch occurred, but I don't know if this is truly meaningful to analyze broken clients. Would any of the available charts be better suited to assess the current status?