-1
1

https://help.openstreetmap.org/questions/34832/bicycle-parkings-display attempts to load some images over HTTP, which are blocked by most modern browsers for mixed content security. How can the comments be changed to load those images over HTTPS instead, so that they are actually loaded?

asked 21 Apr '15, 18:57

Nemo_bis's gravatar image

Nemo_bis
344613
accept rate: 0%

edited 21 Apr '15, 22:14

aseerel4c26's gravatar image

aseerel4c26 ♦
32.1k16239551

For general OSQA questions try http://meta.osqa.net/

(21 Apr '15, 22:03) SomeoneElse ♦

@SomeoneElse: well, yes, but it directly effects us, so why not shortly answer this here (with "meta" tag)?

(21 Apr '15, 22:14) aseerel4c26 ♦

@SomeoneElse, this is a downstream issue.

(21 Apr '15, 22:15) Nemo_bis

instead of e.g.

   http://help.openstreetmap.org/upfiles/Screen_Shot_2014-07-12_at_10.39.23_pm.png

the image URL should be (an URL relative to this site)

   /upfiles/Screen_Shot_2014-07-12_at_10.39.23_pm.png

(Note: this specific image got lost during the last software update, it is not available on the server - I am just using it as example)

However, editing other people's comments is only possible for moderators AND even if that is possible it is not possible to save a comment which exceeds the comment length limit (it only has this length because it was an "answer" before and was converted into a comment).

permanent link

answered 21 Apr '15, 22:13

aseerel4c26's gravatar image

aseerel4c26 ♦
32.1k16239551
accept rate: 17%

edited 21 Apr '15, 22:15

Thanks. How to put (editable) comments with broken images in a queue for moderators to fix?

(21 Apr '15, 22:17) Nemo_bis

@Nemo_bis: I do not know - somehow by a side channel (e.g. wiki or user mail). However, much work for ... hmm.. not that much gain. Rather someone should take the time to fix the software code of the image embedding/upload feature! It is no hard task (relatively), I guess.

I occasionally edit such comments/answers/questions, but only when I am doing any other thing (also to not needlessly push this question up on the main page again).

(21 Apr '15, 22:28) aseerel4c26 ♦
1

@Nemo_bis what you need to do I think is:

o provide lots of helpful advice on this site

o get lots of reputation

o get the ability to edit answers and comments

o make the changes yourself.

Please don't try and make other people "fix" things that you regard as a problem but they may not. Lots of things "need" to be fixed (amongst which there's a whole world out there waiting to be mapped). Everyone in the OSM world is a volunteer, giving up their free time. Your "sense of entitlement" here seems not to understand that.

(21 Apr '15, 22:38) SomeoneElse ♦

Well, I've made several thousands URLs protocol relative in protected Wikimedia projects pages... it took years since http://blog.wikimedia.org/2011/09/27/protocol-relative-urls-enabled-on-all-wikimedia-foundation-wikis/ It's not something you can do automatically, in general. But yes, if most unsecure resources are from this domain (or few other domains known to work over https) then a programmatic solution may be possible. Probably easier to do a mass replacement in the database, though. :)

(21 Apr '15, 22:39) Nemo_bis

@SomeoneElse, sorry, I don't understand your point. My habit is that errors and bugs get reported and tracked for eventual fix. Maybe it's a wiki thing, but there's no "entitlement" in that. I don't expect anything from you.

(21 Apr '15, 22:43) Nemo_bis
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • 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:

×53
×27
×7

question asked: 21 Apr '15, 18:57

question was seen: 5,445 times

last updated: 21 Apr '15, 22:43

powered by OSQA