Troubleshooting involves many aspects of the system. For common issues and their solutions, refer to the following topics.

Can't see unload events when using the sendBeacon API on Safari 11 (and later)

An issue with Safari 11.1 (and later) prevents the sendBeacon API from executing successfully. Instead, you can use the XMLHttpRequest API. For updates about how Apple plans to address the issue, see

Website headers prevent Tealeaf Web SDK from sending data

If you set the following heading on the web application, the Tealeaf Web SDK cannot send data.

#Apache X-XSS measures
Header set X-XSS-Protection “1; mode=block”
Header always append X-Frame-Options SAMEORIGIN
Header set X-Content-Type-Options nosniff

When you set Header set Content-Security-Policy “default-src ‘self’;”, AJAX calls are only allowed to the same website as the original website. For this reason, AJAX Posts from the Tealeaf Web SDK fail.


You have two options for solving the issue:

  • Add default-src ‘self’ ‘tealeafcloud end point url’ so that POSTs are allowed to the Tealeaf end point. When you change your configuration whitelist Tealeaf cloud end point URL, the Web SDK can send data to the Tealeaf servers without any conflicts.
  • Build a proxy on your website that receives and redirects the Web SDK POST to the collector.