CORS errors occur when the client-side code running in the web browser requests data from a domain that is different from the domain of the API server. This is a security feature implemented by web browsers to prevent malicious websites from accessing user data on other websites.
When using Windows Auth on IIS with .Net 6 API, the API server may not correctly handle the CORS headers in the response, resulting in the client-side code being blocked from accessing the data. Kestrel, on the other hand, functions properly because it does not have the same level of security restrictions as IIS.
To resolve this issue in IIS, you may need to configure the API server to explicitly allow cross-origin requests from the client-side code. This can be done by adding the appropriate CORS headers to the response.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2023-07-16 01:30:24 +0000
Seen: 13 times
Last updated: Jul 16 '23
The content inside my buttons is not visible on the screen.
What causes peep and pop operations to produce invalid outputs?
What does the message "No tests found" from playwright VSCode mean?
Why does SVG fail to display in Safari, but functions properly in Chrome?
How to use hyperlinks in SharePoint List within Teams?
What is the meaning of the build error message "NoClassDefFoundError: org/apache/xpath/XPathAPI"?
What is the correct way to load the jQuery fullcalendar plugin in a div that is not visible?