Chromium Embedded Framework (CEF)  122.1.5+gf09a9bc+chromium-122.0.6261.29
cef_origin_whitelist.h File Reference
#include "include/cef_base.h"

Functions

bool CefAddCrossOriginWhitelistEntry (const CefString &source_origin, const CefString &target_protocol, const CefString &target_domain, bool allow_target_subdomains)
 Add an entry to the cross-origin access whitelist. More...
 
bool CefRemoveCrossOriginWhitelistEntry (const CefString &source_origin, const CefString &target_protocol, const CefString &target_domain, bool allow_target_subdomains)
 Remove an entry from the cross-origin access whitelist. More...
 
bool CefClearCrossOriginWhitelist ()
 Remove all entries from the cross-origin access whitelist. More...
 

Function Documentation

◆ CefAddCrossOriginWhitelistEntry()

bool CefAddCrossOriginWhitelistEntry ( const CefString source_origin,
const CefString target_protocol,
const CefString target_domain,
bool  allow_target_subdomains 
)

Add an entry to the cross-origin access whitelist.

The same-origin policy restricts how scripts hosted from different origins (scheme + domain + port) can communicate. By default, scripts can only access resources with the same origin. Scripts hosted on the HTTP and HTTPS schemes (but no other schemes) can use the "Access-Control-Allow-Origin" header to allow cross-origin requests. For example, https://source.example.com can make XMLHttpRequest requests on http://target.example.com if the http://target.example.com request returns an "Access-Control-Allow-Origin: https://source.example.com" response header.

Scripts in separate frames or iframes and hosted from the same protocol and domain suffix can execute cross-origin JavaScript if both pages set the document.domain value to the same domain suffix. For example, scheme://foo.example.com and scheme://bar.example.com can communicate using JavaScript if both domains set document.domain="example.com".

This method is used to allow access to origins that would otherwise violate the same-origin policy. Scripts hosted underneath the fully qualified |source_origin| URL (like http://www.example.com) will be allowed access to all resources hosted on the specified |target_protocol| and |target_domain|. If |target_domain| is non-empty and |allow_target_subdomains| is false only exact domain matches will be allowed. If |target_domain| contains a top- level domain component (like "example.com") and |allow_target_subdomains| is true sub-domain matches will be allowed. If |target_domain| is empty and |allow_target_subdomains| if true all domains and IP addresses will be allowed.

This method cannot be used to bypass the restrictions on local or display isolated schemes. See the comments on CefRegisterCustomScheme for more information.

This function may be called on any thread. Returns false if |source_origin| is invalid or the whitelist cannot be accessed.

◆ CefClearCrossOriginWhitelist()

bool CefClearCrossOriginWhitelist ( )

Remove all entries from the cross-origin access whitelist.

Returns false if the whitelist cannot be accessed.

◆ CefRemoveCrossOriginWhitelistEntry()

bool CefRemoveCrossOriginWhitelistEntry ( const CefString source_origin,
const CefString target_protocol,
const CefString target_domain,
bool  allow_target_subdomains 
)

Remove an entry from the cross-origin access whitelist.

Returns false if |source_origin| is invalid or the whitelist cannot be accessed.