You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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)
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
5971635/55c707be-338a-4505-a9db-933e08e8c872">)
Versions (please complete the following information):
Please let me know if you need any other info
The text was updated successfully, but these errors were encountered: