# CDN incapaz de acessar ativos da origem

**URL:** <https://meta.discourse.org/t/cdn-unable-to-access-assets-from-origin/72560>\
**Category:** Product Support\
**Created:** [22 Outubro , 2017 10:58 UTC](https://meta.discourse.org/t/cdn-unable-to-access-assets-from-origin/72560 "2017-10-22T10:58:34Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![disc](https://avatars.discourse-cdn.com/v4/letter/d/f6c823/32.png) [@disc](https://meta.discourse.org/u/disc)\
**Post date:** [22 Outubro , 2017 10:58 UTC](https://meta.discourse.org/t/cdn-unable-to-access-assets-from-origin/72560/1 "2017-10-22T10:58:34Z")

</div>

“./launcher rebuild app” generates brotli-compressed asset files with file extension “.js.br”. However, when “view source” in the browser, the asset files all have extension “.br.js”. The mismatch of file names causes 404s for CDN, as a result the browser can’t download those files either.

For example, one of the asset files shows in browser “view source” as,

```plaintext
<link rel='preload' href='https://d5e4emqtwppd2.cloudfront.net/assets/locales/en-692973624e3f492c9c0634e89f74ffa930b18c27832c1c7d9ca16864c8da12ac.br.js' as='script'/>

```

But inside the container the files actually look like this:

```plaintext
# ls /var/www/discourse/public/assets/locales/en-692973624e3f492c9c0634e89f74ffa930b18c27832c1c7d9ca16864c8da12ac.*
/var/www/discourse/public/assets/locales/en-692973624e3f492c9c0634e89f74ffa930b18c27832c1c7d9ca16864c8da12ac.js
/var/www/discourse/public/assets/locales/en-692973624e3f492c9c0634e89f74ffa930b18c27832c1c7d9ca16864c8da12ac.js.br
/var/www/discourse/public/assets/locales/en-692973624e3f492c9c0634e89f74ffa930b18c27832c1c7d9ca16864c8da12ac.js.gz
/var/www/discourse/public/assets/locales/en-692973624e3f492c9c0634e89f74ffa930b18c27832c1c7d9ca16864c8da12ac.js.map

```

This happens when using AWS Cloudfront as the CDN provider. When CDN is disabled, it seems to work (at least for Chrome).

---

_[View the full topic](https://meta.discourse.org/t/cdn-unable-to-access-assets-from-origin/72560)._