The following question contains a screenshot:

So far so good. The image URL is https://i.sstatic.net/xMbSu.png and as attempt to make it show in https as well, someone edited the protocol out, leaving only //i.sstatic.net/xMbSu.png as the URL. Now this works perfectly in any browser, but problem is the app is not a browser so it's showing broken image: (with the alt as text)

Can this please be fixed?

Test case: (it is without a protocol, use to reproduce the bug)

iOS app version 0.1.21 for me, if android app user can also confirm please do and let me know.

  • 4
    Surprisingly, it all works as designed - no protocol means "use the same protocol", so it also means "don't use any protocol when viewed in a way that does not involve any"... App did exactly what editor told it to do. Of course it's not what we want or expect, but technically it is the only valid result.
    – Mołot
    Commented Feb 26, 2014 at 15:45
  • @Mołot the app should add protocol manually, the bug is in the app not in the HTML or anything else. Commented Feb 26, 2014 at 15:46
  • From the "what would I want to see happening" point of view you are right. From the "what section 4.2 of RFC 3986 says" current behavior seems proper (if unwanted) and the bug is in the post.
    – Mołot
    Commented Feb 26, 2014 at 16:04

1 Answer 1


This will be fixed in 0.1.23.

This was an interesting problem. The page was loading with no base URL. Providing the question/answer link as a base URL fixed image loading but broke prettify which was loaded from a file:/// URL. I ended up setting up an NSURLProtocol to serve prettify off a custom hostname.

  • 1
    Cheers, didn't imagine it's so complex behind the scenes! :) Commented Feb 26, 2014 at 23:30
  • Installed 0.1.23 now and confirm it is fixed. Commented Feb 28, 2014 at 8:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .