This is part of #378, since this is something possible in D8.2.x: https://www.drupal.org/node/2715637
As of Drupal 8.2, it's possible to opt in a particular site to enable CORS for responses served by Drupal.
(This is particularly helpful for fully decoupled Drupal sites which have JS that needs to talk to a Drupal 8 site's REST API. In such cases, that Drupal 8 instance often runs on a separate domain. Due to the same origin policy those requests will be blocked by the browser.)
This is not enabled by default because there are security consequences.
New in default.services.yml:
# Configure Cross-Site HTTP requests (CORS). # Read https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS # for more information about the topic in general. # Note: By default the configuration is disabled. cors.config: enabled: false # Specify allowed headers, like 'x-allowed-header'. allowedHeaders: [] # Specify allowed request methods, specify ['*'] to allow all possible ones. allowedMethods: [] # Configure requests allowed from specific origins. allowedOrigins: ['*'] # Sets the Access-Control-Expose-Headers header. exposedHeaders: false # Sets the Access-Control-Max-Age header. maxAge: false # Sets the Access-Control-Allow-Credentials header. supportsCredentials: falseNote particular that
enabled: falsekey-value pair!
Recent comments
I am withdrawing my question for the following reason: https://forum.backdropcms.org/comment/8960#comment-8960
Error when trying to check for updates
My hosting is located in a country that blocks numerous online resources, so I am not surprised that updates and modules are unavailable. However, everything works perfectly on a local server...
Unable to run update - fails with Connection timed out
UPDATE: I fixed the errors that I found in the logs. They were related to deleting an old blog content type pulled over from Drupal that was still referenced in one of the layouts. I updated...
missing "add block" in custom layout