Open djskinner opened 1 month ago
@bugsnag/browser
bundle size diffMinified | Minfied + Gzipped | |
---|---|---|
Before | 45.89 kB |
13.78 kB |
After | 46.96 kB |
14.02 kB |
± | ⚠️ +1,073 bytes |
⚠️ +242 bytes |
Generated by :no_entry_sign: dangerJS against d38cc52145d67ff10541d95f828018b36bc5e6cf
Do we also need to set this in the
delivery-x-domain-request
package? I suppose IE8 and 9 won't support an integrity header?
No, XDomainRequest is only available on ie8 and ie9 neither which support the necessary APIs for calculating and setting the integrity header. even ie11 is excluded because it doesn't have full native promise support, hence the typeof Promise !== 'undefined' && Promise.toString().indexOf('[native code]') !== -1
check.
Goal
Add Bugsnag-Integrity request header (where required APIs are available) and implement the
sendPayloadChecksums
core config option to allow opting out of this behavior.Bugsnag-Integrity headers are set by default unless the
endpoints
configuration option is set, in which case they are disabled. This behavior can be overriden with the newsendPayloadChecksums
config option.Design
sendPayloadChecksums
was chosen to avoid possible CORS issues where custom endpoints are being used and they are not configured to accept the newBugsnag-Integrity
in requests.Changeset
sendPayloadChecksums
core config optionBugsnag-Integrity
in delivery-fetch, which is used in@bugsnag/web-worker
.Bugsnag-Integrity
in delivery-xml-http-request, which is used in@bugsnag/browser
.Testing