| loio |
|---|
| 64bdd33d236340908fe2659162492b39 |
view on: demo kit nightly build | demo kit latest release
There are certain scenarios in which the Support Assistant does not behave as expected. In this section you can find tips on how to recognize and resolve some of these cases.
|
Support Assistant Behavior |
Root Cause |
Solution |
|---|---|---|
|
What does it mean when the following errors appear in the browser console? "Access to XMLHttpRequest at <URL> from origin <ORIGIN> has been blocked by the CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource." |
This usually happens when serving OpenUI5 from a different origin. The Support Assistant tries to load support rule definitions from there, but cannot load them - a 404 response is sent by the origin server. The issue is usually caused by missing or misconfigured CORS headers on the 404 response specifically. Besides some support rules not being loaded, this should not affect normal operation of Support Assistant. |
OpenUI5 library owners are encouraged to provide a For more information, see Create a Ruleset for a Library and Content Security Policy. |
|
When you choose a custom location, you get an error message: 'The syntax of the location address is incorrect. The correct syntax is ... '. |
URL doesn't match the protocol of the application. |
If the application is HTTP, the location should also be HTTP. If it is HTTPS, the location should be HTTPS. Also, the URL should end in sap/ui/support/. |
|
Temporary rules are not available in the current environment due to Content Security Policy (CSP) restrictions. |
Content Security Policy is forbidding the execution of temporary rules. |
Run the Support Assistant in a development environment, where the |