External image sources being re-written (FIXED)

parkeristyping · ‎Sep 12, 2016

UPDATE: Seems like this was a bug and has been fixed.

I’m finding that the domain of external image sources are being overwritten to my HubSpot domain. (By “external”, I just mean images that I’ve never uploaded to HubSpot. E.g. images hosted on a totally separate Cloudfront distribution.)

I have a few questions about this:

Do others see this behavior? Did you perhaps see that it just started this weekend (9/10/2016)?
Anyone know if this is intended behavior or have more details/docs on it?
Anyone know a clean way to get around it? A configuration setting, maybe?

For more detail, please see the coded file below (most of which is HubSpot-supplied boilerplate). When I create and publish a page using this template, the Wikipedia image gets re-written to “https://myhubspot.domain.com/wikipedia/commons/c/c0/OSIRIS-REx_Artist’s_conception.png”.

I use the Wikipedia image just to demonstrate this happens with any random external image.

<!doctype html>
<html>
    <head>
        <meta charset="utf-8">
        <title>{{ content.html_title }}</title>
        <meta name="description" content="{{ content.meta_description }}">
        {{ standard_header_includes }}
    </head>
    <body>
        <!-- begin only non-boilerplate line. -->
        <img src="https://upload.wikimedia.org/wikipedia/commons/c/c0/OSIRIS-REx_Artist%E2%80%99s_conception.png" />
        <!-- end only non-boilerplate line. -->
        {{ standard_footer_includes }}
    </body>
</html>

Thanks,
Parker

Dadams · ‎Sep 12, 2016

@parkeristyping is there an example page that you could send me that you’re seeing this on? We made some changes recently related to how HubSpot hosted files would work but it shouldn’t have affected completely external files.

parkeristyping · ‎Sep 12, 2016

@dadams Yep. Here’s an example page created from the exact HubL template I posted above: [edit: removed this because it’s dead now]

Dadams · ‎Sep 12, 2016

Thanks @parkeristyping, I passed this over to our Content team and it looks like they’re already working on a fix for this. I’ll reply here when I have any updates on this.

parkeristyping · ‎Sep 13, 2016

@dadams it seems like this has been fixed now. Thanks for your help.

APIs & Integrations