|
Not a question, but a hint for people who may fix this. Feel free to move this comment to any other place, where you think it belongs. Loading https://osm.orgbrings some TLS related problems. First one: The certificate CN is wrong. This is annoying, but passable. Major one: Only the standard map and MapQuest Open work, when you forbid loading cleartext content on TLS websites – which is generally a good idea. For example the bicycle map is included via http://a.tile.thunderforest.com/cycle/…,although https://a.tile.thunderforest.com/cycle/…would work as well. Unnecessarily, to be able to use the bicycle map, I have to instruct my browser to transmit HTTP requests in an HTTPS context. Maybe you want to fix this, as it should be not such a big deal. |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 07 Aug '15, 17:57
question was seen: 1,035 times
last updated: 10 Aug '15, 07:24
Regarding the first issue: https://osm.org is not an official OSM domain so there is nothing OSM can do about it. The second issue sounds like it can be fixed so try to report it at https://github.com/openstreetmap/openstreetmap-website
whois lists OSMF as the admin organization for osm.org it doesn't get much more official than that.
Interesting. It has been an unofficial domain in the past IIRC.