# Access-Control-Allow-Origin: \* in assets

**URL:** <https://community.prismic.io/t/access-control-allow-origin-in-assets/13786>\
**Category:** Developing with Prismic\
**Tags:** nuxtjs, javascript\
**Created:** [July 31, 2023, 1:19pm UTC](https://community.prismic.io/t/access-control-allow-origin-in-assets/13786 "2023-07-31T13:19:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tech.microsites.plat](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@tech.microsites.plat](https://community.prismic.io/u/tech.microsites.plat)\
**Post date:** [July 31, 2023, 1:19pm UTC](https://community.prismic.io/t/access-control-allow-origin-in-assets/13786/1 "2023-07-31T13:19:11Z")

</div>

Hi!

Would it be possible to add `Access-Control-Allow-Origin: *` header to javascript assets that are used by browser. It will help us to see errors in these third-party scripts. Currently we can see only `Script error` in our logs and [Datadog advises](https://docs.datadoghq.com/real_user_monitoring/browser/collecting_browser_errors/?tab=npm#script-error) to do these steps to reveal the errors. For example, google analytics scripts do the same thing.

As a third-party script from Prismic I see these 2 files:

- [https://static.cdn.prismic.io/prismic.min.js?repo=repo-name&new=true](https://static.cdn.prismic.io/prismic.min.js?repo=repo-name&new=true)
- [https://prismic.io/prismic-toolbar/4.0.9/toolbar.js](https://prismic.io/prismic-toolbar/4.0.9/toolbar.js)

---

<div class="post-metadata">

**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\
**Post date:** [July 31, 2023, 2:38pm UTC](https://community.prismic.io/t/access-control-allow-origin-in-assets/13786/2 "2023-07-31T14:38:11Z")

</div>

Hey @tech.microsites.plat, have you checked out this similar post?

> [@Request header field prismic-ref is not allowed by Access-Control-Allow-Headers in preflight response](https://community.prismic.io/t/request-header-field-prismic-ref-is-not-allowed-by-access-control-allow-headers-in-preflight-response/1723):
>
> Hi guys, I have a CORS problem, can you help me? The question is: Access to fetch at 'https://repository\_url...' from origin 'https://my\_domain..' has been blocked by CORS policy: Request header field prismic-ref is not allowed by Access-Control-Allow-Headers in preflight response. Thanks.

---

<div class="post-metadata">

**Author:** ![tech.microsites.plat](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@tech.microsites.plat](https://community.prismic.io/u/tech.microsites.plat)\
**Post date:** [August 1, 2023, 6:38am UTC](https://community.prismic.io/t/access-control-allow-origin-in-assets/13786/4 "2023-08-01T06:38:51Z")

</div>

Hey Pau, in this case it's more about assets like `prismic.min.js` and `toolbar.js` files. In the post you sent I see discussions about graphQL requests.  
My guess is that this case will be easy since it's a matter of adding one header to these static assets.