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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After updating our Application to v118 CORS Policy is not working #3604

Closed
ajaykundu opened this issue Nov 15, 2023 · 1 comment
Closed

After updating our Application to v118 CORS Policy is not working #3604

ajaykundu opened this issue Nov 15, 2023 · 1 comment
Labels
bug Bug report

Comments

@ajaykundu
Copy link

ajaykundu commented Nov 15, 2023

After Updating the acrobat to latest version 118. we started having error in CORS Policy

To Reproduce
Facing the Issue in our application while launching some of the network calls and having the following error.

Access to XMLHttpRequest at 'https://createpdf.acrobat.com/createpdf/api/base_uris?force=true&_=1700027770598' from origin 'https://rna-resource.acrobat.com' has been blocked by CORS policy: Request header field x-request-id is not allowed by Access-Control-Allow-Headers in preflight response.

Is there any change in CefAddCrossOriginWhitelistEntry API .

We are moving from version 104 to 118.

Expected behavior
There should be no error in CORS Policy.

[Screenshots](<img width="1728" alt="Screenshot 2023-11-15 at 4 24 36 PM" src="https://github.com/chromiumembedded/cef/assets/2
Screenshot 2023-11-15 at 4 24 36 PM
5971635/55c707be-338a-4505-a9db-933e08e8c872">)

Versions (please complete the following information):

  • OS: [Mac & Windows]
  • CEF Version: [e.g. 118.0.5993.119]
    Please let me know if you need any other info
@ajaykundu ajaykundu added the bug Bug report label Nov 15, 2023
@ajaykundu ajaykundu changed the title After updating Acrocef to v118 CORS Policy is not working After updating our Application to v118 CORS Policy is not working Nov 15, 2023
@magreenblatt
Copy link
Collaborator

Request header field x-request-id is not allowed by Access-Control-Allow-Headers in preflight response.

The recommended solution is to fix your server as explained in this error message.

Is there any change in CefAddCrossOriginWhitelistEntry API . We are moving from version 104 to 118.

Perhaps the restriction is new in Chromium since 104, as CefAddCrossOriginWhitelistEntry was never intended to help with Access-Control-Allow-Headers errors. See #2918 (comment)

@magreenblatt magreenblatt closed this as not planned Won't fix, can't repro, duplicate, stale Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report
Projects
None yet
Development

No branches or pull requests

2 participants