CORS Support for API Use

julian

Hi @David-Sargrad, have you tried adding a specific domain to that list? While the * value is a valid header, I am not certain whether that value there would be considered valid.

phenomlab

@julian This is correct. I needed to do the same for my OGProxy to work

David Sargrad

Thanks Guys. I'll try that. Right now I'm on localhost, so presumably:
http://localhost

should work?

David Sargrad

I've tried both http://localhost

and http://localhost:4567

However I still get the same problem.

I can browse to this URL however..

julian

What site are you making the call from?

PitaJ

Chrome does not support CORS for localhost: https://stackoverflow.com/questions/10883211/why-does-my-http-localhost-cors-origin-not-work

David Sargrad

@julian I'm not sure I understand the question. I am on my development machine. I am running a local instance of nodebb on that same machine.

@PitaJ I did see some interesting options listed at the location you linked. I'll try them.

I would have thought that this is something that many NodeBB developers (those that want to use the NodeBB API) would have seen and learned to address in a standard way.

David Sargrad

Ok. I find this interesting, and it better helps me to understand @julian
https://stackoverflow.com/questions/45975135/access-control-origin-header-error-using-axios

The "site" that I am calling from is likely my "react app" which is running at http://localhost:3000

Of specific interest is this persons description
https://stackoverflow.com/a/64137023

However this also explains why I thought "*" should work as in the following:

app.get('/hello', function (req, res) {
    res.header("Access-Control-Allow-Origin", "*");
    res.send('Hello World');
})

I've developed such node express services before, and have always used this practice when I want to allow cross origin requests on the localhost.

David Sargrad

I also like the "nginx" option. I may try this eventually.

http://www.pierre-beitz.eu/2017/01/24/Dealing-with-CORS-in-a-Development-Environment-Using-a-Reverse-Proxy.html

In fact the example shown in the link above is exactly the scenario I am using with NodeBB's API.

David Sargrad

Yay!! It worked when I used the ACP to set the Access-Control-Allow-Origin field to http://localhost:3000.

I would recommend looking at allowing "*". This is a common CORs practice, particularly in a development environment.