Related

Can i set a CNAME rules for my Spaces Storag such as S3 ? Question Question
How to restrict object access to only certain origins through CORS policy in Spaces? Question Question

Question

Why can I use "http://localhost:PORT" with CORS in Spaces?

Posted January 24, 2018 10.6k views
Object Storage

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.

Add a comment
By:
NetOperatorWibby
Add a comment
1 comment
  • atf104 January 30, 2019
    Reply Report

    I was trying to enter CORS for localhost on a Space, and it appears the UI is still not handling (you have to upload an XML file still). Does this plan on ever getting fixed?

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.

×
5 answers
asb February 28, 2018

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 s3cmd you can run:

  • s3cmd setcors cors.xml s3://example-space

Where the contents of the cors.xml file contains your CORs configurations in XML format. For example:

<CORSConfiguration>
 <CORSRule>
   <AllowedOrigin>http://localhost:3000</AllowedOrigin>

   <AllowedMethod>PUT</AllowedMethod>
   <AllowedMethod>POST</AllowedMethod>
   <AllowedMethod>DELETE</AllowedMethod>

   <AllowedHeader>*</AllowedHeader>
 </CORSRule>
</CORSConfiguration>
Reply Report
  • jor3l April 19, 2018

    any news on this? I don’t want to use another tool just for this.

    Reply Report
  • NetOperatorWibby April 24, 2019

    More than a year later and I had to get a CDN up for my wife’s blog so I went through this process. Turns out the “example-space” in s3://example-space has to be the name you chose for your Space.

    This roundabout way of adding localhost support worked but it’d be much appreciated if the UI could do it.

    Reply Report
mihae06f9f44effc54818bb508 March 27, 2019

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

Reply Report
hmaesta October 17, 2018

CORS options are now available thru DigitalOcean Dashboard.
If you are facing this problem:

  1. Go to https://cloud.digitalocean.com/spaces
  2. Select your Space
  3. Go to Settings tab
  4. On “CORS Configurations”, click on the “+” (Plus) button

Create a new configuration with this values:

  • Origin: *
  • Allowed Methods: GET
  • Allowed Headers: Click “Add header” an them: *
  • Save options

Should work.

Reply Report
zeltiche July 16, 2018

There are no pre-built s3cmd binaries for Windows.

So the depth of things we need to do to set CORS for Spaces for local development:

  • Cant set CORS because of rules too strict, must use s3cmd:
  • Must get s3cmd. Cannot get s3cmd because no windows binaries.
  • Must build s3cmd from source. Cannot build s3cmd from source because it requires Python 2.x.
  • Must download Python 2.x in system. Must vet python for development. If your stack does not include Python. Must learn python.

=|

Reply Report
caihedoro June 22, 2018
[deleted]
Reply Report
Richelly July 26, 2018

With me Localhost works only after set a certified on php.ini.

https://curl.haxx.se/ca/cacert.pem

curl.cainfo = “pathtocert\cacert.pem”

I hope help you guys!

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help