Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect planet.openstreetmap.org to HTTPS #200

Closed
pnorman opened this issue Mar 2, 2018 · 11 comments
Closed

Redirect planet.openstreetmap.org to HTTPS #200

pnorman opened this issue Mar 2, 2018 · 11 comments

Comments

@pnorman
Copy link
Collaborator

@pnorman pnorman commented Mar 2, 2018

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

This comment has been minimized.

Copy link

@SomeoneElseOSM SomeoneElseOSM commented Mar 2, 2018

@grischard

This comment has been minimized.

Copy link

@grischard grischard commented Mar 5, 2018

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

This comment has been minimized.

Copy link
Member

@tomhughes tomhughes commented Mar 5, 2018

Works for me.

This was referenced Mar 7, 2018
This was referenced Apr 2, 2018
@grischard

This comment has been minimized.

Copy link

@grischard grischard commented Apr 2, 2018

Done tasks 1 and 4.

@grischard

This comment has been minimized.

Copy link

@grischard grischard commented Apr 6, 2018

Afaict 2 is done too.

@grischard

This comment has been minimized.

Copy link

@grischard grischard commented Apr 14, 2018

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

@grischard

This comment has been minimized.

Copy link

@grischard grischard commented May 11, 2018

@tomhughes tomhughes closed this May 11, 2018
@mmd-osm

This comment has been minimized.

Copy link

@mmd-osm mmd-osm commented May 12, 2018

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.