...
...
| Info |
|---|
You receive an error message when the reference JAR file is incorrect or when the asset is not found. When you create an API from an existing project, the reference assets, including error pipelines and accounts, located in various folders or directories, as well as and also the associated JAR files linked to the accounts, are automatically updated.
|
...
To test the Try it out button for your API: Discovering APIs in the API Catalog
Troubleshoot for “Try It Out” functionality
...
Areas to troubleshoot when an error occurs | Error messages in the console | Resolution |
|---|
CORS | Access to fetch is blocked by CORS policy: Request header field authorization is not allowed by Access-Control-Allow-Headers in preflight response.
| Check if the CORS Restriction policy is enabled. The default CORS Restriction policy can be enabled in the Settings Panelfrom the Portal Manager, Enable Try Me checkbox. Check Access Control Request Headers because it is a mandatory field if it not configured it can give an error.
| Info |
|---|
The CORS policy with a default setting provides a standard configuration. |
|
Network Failure | Network Error
| Check the Network Connectivity. |
URL scheme in CORS settings dialogue box | Mixed Content: The page<>was loaded over HTTPS, but requested an insecure resource<>. This request has been blocked; the content must be served over HTTPS.
| Use only “http” or “https” for the CORS request. Check if the page is loaded over HTTPS matches the URL HTTPS scheme in the CORS request. If your page was loaded over HTTPS, and requested an insecure resource with HTTP, then an error occurs
|
FeedMaster and Load Balancer | Failed to load resource: net::ERR_NAME_NOT_RESOLVED
| |
...
