Safari doesn’t respect my wildcard rule in CORS but Firefox and Chrome do. None of the suggestions in this StackOverflow post helped either: https://stackoverflow.com/questions/16824661/cors-request-not-working-in-safari/39875236.
I feel like this could be remedied if Spaces was configured to allow a URL without a TLD.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
Thanks for flagging this issue for us. It looks like the input validation in our control panel is a bit too strict here. As a work-around until this experience is improved, you can create CORs configurations for Spaces using the API for origins without a TLD. For example, using
s3cmdyou can run:
Where the contents of the
cors.xmlfile contains your CORs configurations in XML format. For example:
So the year has gone by and it still isn’t possible to set http://127.0.0.1:12345 as a cors via the control panel
CORS options are now available thru DigitalOcean Dashboard. If you are facing this problem:
Create a new configuration with this values: