Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

SharePoint requests requiring Cross-Origin Resource Sharing (CORS) policy #9650

Open
1 of 9 tasks
sagarkhatriseclore opened this issue Apr 22, 2024 · 0 comments
Open
1 of 9 tasks

Comments

@sagarkhatriseclore
Copy link

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

SharePoint Add-ins

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

  • 馃挜 Internet Explorer
  • 馃挜 Microsoft Edge
  • 馃挜 Google Chrome
  • 馃挜 FireFox
  • 馃挜 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

No response

Issue description

Hi Team,

I am writing to bring to your attention an issue we have encountered issue with SharePoint and the recent behavior of its requests requiring Cross-Origin Resource Sharing (CORS) policy.

We have configured Seclore's Addin in SharePoint, sharepoint accesses assets stored in our AWS cloud. However, we have recently observed that SharePoint is firing multiple requests for the same assets. Interestingly, only some of these requests require the CORS policy. This is a deviation from our previous experience, where we did not encounter any requests necessitating the CORS policy.

This change in behavior has raised concerns for us, as it seems to be causing request to fail due with error "Access has been blocked by CORS policy, No 'Access-Control-Allow-Origin' header is present on the requested resource.". We are uncertain whether there has been a modification in the way requests are handled by SharePoint, particularly regarding the CORS policy.

Could you please provide us with insights into any recent changes or updates that might have caused this issue?

Thank you for your attention to this matter. We look forward to your prompt response and assistance in resolving this issue.

Thank you!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant