Capturing cross-domain script errors

This documentation is for version 6 of the BugSnag JavaScript notifier. We recommend upgrading to the latest release using our Upgrade guide. Documentation for the current release can be found here.

BugSnag ignores cross domain script errors by default, because they contain no useful information. You can fix this by loading your script using CORS.

Overview

Add the CORS header to your web-server.
```
Access-Control-Allow-Origin: *
```

Add the crossorigin attribute to your script tag.

<script src="//cdn.example.com/site.js" crossorigin></script>

For more information, see our blog post.

Webserver instructions

nginx

Use the following configuration snippet. Replace /assets/by the path that contains your javascript.
```
location /assets/ {
  add_header 'Access-Control-Allow-Origin: *';
}
```

Amazon S3

Log into the S3 Console
Open your bucket
Click “Properties” in the top right.
Under “Permissions” click “Add CORS Configuration”.

Use the following policy

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <CORSRule>
        <AllowedOrigin>*</AllowedOrigin>
        <AllowedMethod>GET</AllowedMethod>
        <MaxAgeSeconds>1209600</MaxAgeSeconds>
    </CORSRule>
</CORSConfiguration>

Amazon Cloudfront

In Cloudfront, under Distribution Settings, Behaviors, click “Create Behavior”.
Set the “Path Pattern” to *
Under “Forward Headers” select “Whitelist” and add “Origin” to the whitelist.
Save the behavior.