Scope of CefAddCrossOriginWhitelistEntry() call

[Plinker1961]

I am using a directory provider that maps content from a shared CDN (e.g., https://my.cdn.com) to the local file system. Testing this feature quickly revealed that content from the directory provider was being blocked due to CORS violations. Not wanting to disable web security (which is a workaround), I sought a cleaner solution. What I found that works is adding a cross-origin whitelist entry using something along the lines of:

Code: Select all

CefAddCrossOriginWhitelistEntry("https://my.application.com", "https", "my.cdn.com", true);

So here are my questions: what is the scope of this CefAddCrossOriginWhitelistEntry call? Global? I presume the answer here is Yes. Will this call impact all browsers currently instantiated as well as those that may be created later while the application is running? Again my assumption is Yes given that CefAddCrossOriginWhitelistEntry has no browser parameter or context.

To clarify, my CEF application uses multiple browser windows/tabs that get created and destroyed regularly, so I just want to double-check my assumptions regarding CefAddCrossOriginWhitelistEntry. Currently I call this only once per source origin (i.e., we have more than one source origin that wants access to the CDN). Hope that makes sense.

Thanks!

[magreenblatt]

Yes, it is set globally.

[Plinker1961]

Thanks!