Welcome
User Guide
Developer guide
Reference Guide
Frequently Asked Questions
Pricing policy
Data retention policy
Draft: Default Space How to upgrade by payment?
How to re-subscribe to an expired DID Space
Connecting to the DID Space using the Gateway Address
Switch the DID Space bound to NFT Blender.
The automatic backup of Blocklet is stuck, how can it be quickly restored?
Fix CORS error when connecting DID Space
Change log
Draft: Purchase DID Space
DID Spaces v0.6.0: OAuth Integration in DID Spaces
DID Spaces v0.5.83: OAuth integrated DID Space
Prod Spaces data retention policy updated
DID Spaces v0.4.26 released: subscription fully adopts pay-as-you-go & supports paid upgrade Default Space
DID Spaces v0.3.75 released: Supports reading and writing component spaces
DID Spaces v1.0.48: 支持预览 post/bookmark/blog/doc
Fix CORS error when connecting DID Space
Overview#
When connecting to a DID Space, you may encounter CORS errors.
The reason is that the target DID Space has disallowed cross-origin requests from this server. To resolve this issue, the DID Space administrator needs to modify the security configuration in the backend.
Prerequisites#
- Access to the DID Spaces Dashboard requires Owner or Admin permissions.
Procedure#
Access the DID Space console:
Locate the security rule configuration and the name of the currently active response header policy.
Open the edit page for the response header policy:
Configure Origin:
As shown above, the Origin only includes one address, and it’s not the Blocklet Server address used previously. Consequently, connections from the Blocklet Server to the DID Space will be blocked by CORS. We can add the Blocklet Server’s address to the Origin, or set the Origin to * (to allow any cross-origin requests):
You can then connect to the DID Space:
