Troubleshooting involves many aspects of the system. For common issues and their solutions, refer to the following topics.
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 https://bugs.webkit.org/show_bug.cgi?id=188329.
If you set the following heading on the web application, the Tealeaf UIC 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 UIC fail.
You have two options for solving the issue:
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 UIC can send data to the Tealeaf servers without any conflicts.
- Build a proxy on your website that receives and redirects the UIC POST to the collector.
Updated 25 days ago