# Images URLs are broken (https: part not being included)

**URL:** <https://meta.discourse.org/t/images-urls-are-broken-https-part-not-being-included/205365>\
**Category:** Support\
**Created:** [October 6, 2021, 3:35pm UTC](https://meta.discourse.org/t/images-urls-are-broken-https-part-not-being-included/205365 "2021-10-06T15:35:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Simon\_Manning](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon_manning/32/198596_2.png) [@Simon\_Manning](https://meta.discourse.org/u/Simon_Manning)\
**Post date:** [October 6, 2021, 4:44pm UTC](https://meta.discourse.org/t/images-urls-are-broken-https-part-not-being-included/205365/4 "2021-10-06T16:44:49Z")

</div>

If the URL format changed without you doing anything, my assumption would be that your server automatically updates Discourse and this was the trigger but I wouldn’t expect the URL comparison you used to be a problem. Unless you’re displaying that URL to users for them to be able to copy, it should work as-is.

A URL beginning “//” uses the same scheme as the document referencing it, i.e. if you successfully visit the page over HTTP, it’s equivalent to “http://”. If you visit the page over HTTPS, it’s equivalent to “https://”

---

_[View the full topic](https://meta.discourse.org/t/images-urls-are-broken-https-part-not-being-included/205365)._