# Why don't images include url protocol?

**URL:** <https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461>\
**Category:** Questions\
**Created:** [September 21, 2018, 6:32pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461 "2018-09-21T18:32:37Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![csblack](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@csblack](https://forum.bubble.io/u/csblack)\
**Post date:** [September 21, 2018, 6:32pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/1 "2018-09-21T18:32:37Z")

</div>

If you save an image in bubble, the url is returned as “//s3…”

Why isn’t it “[https://s3](https://s3)…”?

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [September 21, 2018, 9:24pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/2 "2018-09-21T21:24:00Z")

</div>

I have no idea why they only store the path part and not the protocol. But that’s what happens.

This tripped me up for the umpteenth time a few days ago. See this thread:

> [@Link Element Broken? What \*IS\* this weird extra Link Destination Pop-up...?](http://forum.bubble.io/t/link-element-broken-what-is-this-weird-extra-link-destination-pop-up/37948):
>
> [EDIT: Solved. I was just “dooing it rong”. See solution. Leaving my post here though as a warning to others not to be such a smarty-pants and assume Bubble won’t usually just “do the right thing.” Derp.] I’m seeing weird behavior in the Link element. I’ve never seen this before. Looks to me like I have this dialog configured entirely correctly, but the Issue Checker is throwing an error. When I click the error, this separate “Link Destination” pop-up appears… But as you can see from the snip…

Read the whole thing down to where @mishav chimes in and I reply. The “solution” marked in this thread works, but Misha points out that it does seem incorrect the way Bubble is handling this.

I’ve got some other more urgent bugs filed right now so I’m not keen to report this, but I don’t understand it either. Just know that, if you want to link out to one of those files you CAN (do it the way I explain in the thread). But if you want to write out the URL as text or something, you’ll have to add the “https:” part yourself.

This might also be an issue if you’re passing such an URL to an external API or something.

Anyway, I’m not sure if it’s _intentional_ that Bubble just stores the path, but clearly the NAME for the field is misleading. The “URL” to the s3 file is not a fully-qualified URL, but is in fact a PATH.

This doesn’t make a lot of sense because I think s3 only allows reference via https: (not http:) so I’m baffled by this if it’s NOT a bug. #shrug

---

<div class="post-metadata">

**Author:** ![neerja](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/neerja/32/29814_2.png) [@neerja](https://forum.bubble.io/u/neerja)\
**Post date:** [September 21, 2018, 10:37pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/3 "2018-09-21T22:37:45Z")

</div>

While clicking on the s3 file’s url within a link element directs to the image successfully, is the issue that file’s url displays path and doesn’t include ‘https’?

 ![file_upload_url](https://us1.discourse-cdn.com/bubble/original/3X/c/d/cd2ab8d026a3a5928ca428869ee52041241454e0.png)

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [September 21, 2018, 10:58pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/4 "2018-09-21T22:58:24Z")

</div>

Pretty much. The question is: Why is it stored this way? (Is there some reason, or is it a bug?)

I’ve run into this in other contexts: For example, I have an API that sends me back a file. The file gets stored in s3. I then do things with the file like create a Rebrandly alias for it. When I ping Rebrandly’s API, I have to send the Rebrandly API an expression like:

`https:my_file_thing's file's URL`

when it seems like it should just be: `my_file_thing's file's URL`

Of course at this point, to change that behavior would be a breaking change.

As Misha pointed out in the other thread, the link element works because one’s browser expands the path correctly:

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/4/0/40c05b7248ca25035e4197588a1844d15bb23516.png)

But this is counter to how one would do URLs in one’s app or how most any API (that accepts a URL argument or whatnot) would have you specify a URL. On the same page I snipped above, for example, I show the URL that is the source of the PDF thing, that URL was sent to an external API as a fully-qualified URL and I store it in my database as a fully qualified URL. And the link I create to it is of course a fully-qualified URL:

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/8/b/8b15a4b109d74b40b2b57529419637bf4ada5400.png)

It’s just… like… why would you do this any other way? 🤪

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [September 21, 2018, 11:02pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/5 "2018-09-21T23:02:40Z")

</div>

At a minimum, the docs and the label on s3 URLs are not correct. This thing IS NOT the file’s URL. It is the file’s PATH.

A non-breaking fix would be to change the NAME of `file's URL` field to `file's path` and make a new field for `file's URL` that is ACTUALLY the fully-qualified URL.

---

<div class="post-metadata">

**Author:** ![csblack](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@csblack](https://forum.bubble.io/u/csblack)\
**Post date:** [September 22, 2018, 12:14am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/6 "2018-09-22T00:14:34Z")

</div>

Correct. The image url may load in your browser, but if you fetch the it from an API, it poses a problem. You have to first prepend the url with https.

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [September 22, 2018, 12:33am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/7 "2018-09-22T00:33:34Z")

</div>

With “https:” 😁

---

<div class="post-metadata">

**Author:** ![seanhoots](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/seanhoots/32/12224_2.png) [@seanhoots](https://forum.bubble.io/u/seanhoots)\
**Post date:** [September 22, 2018, 2:16am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/8 "2018-09-22T02:16:33Z")

</div>

Just wanted to add that bubble not saving images with **https:** has been a hell for Dropsource users.  
If you go to their forum and search https you will see a lot of discussions on it like this [thread](https://forum.dropsource.com/t/resolved-sending-images-to-and-getting-images-from-bubble-to-dropsource-edited/415/37).

So if you’re developing in Dropsource and using bubble as backend, you always have to create a workflow in bubble to prepend the https: or you have to create an action in dropsource to do that before you could use bubble images.

I still don’t know the reason why bubble does it this way.

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [September 22, 2018, 2:43am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/9 "2018-09-22T02:43:35Z")

</div>

It’s derpy in the extreme. Somebody should file a formal bug report as I can’t see any reason for this either. (But I got my own bugs, yo, and Neerja is tired of hearing from me. 😜)

---

<div class="post-metadata">

**Author:** ![seanhoots](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/seanhoots/32/12224_2.png) [@seanhoots](https://forum.bubble.io/u/seanhoots)\
**Post date:** [September 22, 2018, 2:54am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/10 "2018-09-22T02:54:02Z")

</div>

> [@keith](#):
>
> Somebody should file a formal bug report as I can’t see any reason for this either.

I’m not sure if we can classify this as a bug. Because i’m very sure it is by design.  
Plus bubble is very aware of it.  
I want to believe there is a good reason they have the current setup.

I’ve brought this up before so I can only hope they add it for us.

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [September 22, 2018, 2:58am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/11 "2018-09-22T02:58:28Z")

</div>

Do not be sure about that. They should just answer the damn question (why). To get that answer still requires a bug report.

---

<div class="post-metadata">

**Author:** ![neerja](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/neerja/32/29814_2.png) [@neerja](https://forum.bubble.io/u/neerja)\
**Post date:** [September 24, 2018, 9:54pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/12 "2018-09-24T21:54:48Z")

</div>

Thanks all. Will review the feature request with devs and post back.

@seanhoots yup, submit your own bug report 🙂

---

<div class="post-metadata">

**Author:** ![momomonet](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/momomonet/32/201935_2.png) [@momomonet](https://forum.bubble.io/u/momomonet)\
**Post date:** [July 17, 2024, 6:24am UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/13 "2024-07-17T06:24:54Z")

</div>

Hi,  
I’m facing the same pb trying to send an image url as a parameter for stripe checkout API call.  
“https:” is missing from the url and i have to add it manually which i think is not a good way.  
Did you find any solution?  
Thank you

---

<div class="post-metadata">

**Author:** ![dpappo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@dpappo](https://forum.bubble.io/u/dpappo)\
**Post date:** [February 5, 2025, 8:52pm UTC](https://forum.bubble.io/t/why-dont-images-include-url-protocol/38461/14 "2025-02-05T20:52:56Z")

</div>

@fede.bubble here’s an idea for a bubble boost that we’re still facing 6 years on
