Troubleshooting CORS Errors in Inspect

In this article you will learn how to investigate CORS errors that are occurring when using the UtiliSync Inspect app.

Look for the origin header in the request headers of the failed network request and see if it is missing.

You can also try the steps below:

Why would the Origin header be missing in just Chrome?

The Origin header is automatically included by browsers in cross-origin requests, so its absence can be unusual. Here are some possible reasons for its absence in Chrome:

1. Same-Origin Requests:
   1. The Origin header is only included in cross-origin requests. If Chrome somehow interprets the request as a same-origin request (even if it's not), it may not include the Origin header.
   2. Check the domain from which the app is being accessed and ensure that Chrome isn't mistakenly treading the request as same-origin due to configurations, like using a different subdomain
2. Extensions or Proxies:
   1. A browser extension, proxy, or VPN might be interfering with or stripping out the Origin header in Chrome. Since Edge doesn't share the same extensions ecosystem as Chrome, this could explain the discrepancy.
   2. Test the login in Incognito Mode (which disables extensions) or check for any VPNs or proxy services.
3. Chrome-Specific Configuration:
   1. Chrome may have stricter policies or settings enabled (perhaps through security or privacy settings) that could suppress certain headers, including Origin . The customer should try resetting Chrome settings or ensuring that any security/privacy extensions aren't affecting requests.