The 'Access-Control-Allow-Origin' header has a value

[dinhnghia]

XMLHttpRequest cannot load http://api.nhamoigioi.xyz/locations/districts. The 'Access-Control-Allow-Origin' header has a value 'http://localhost:4200' that is not equal to the supplied origin. Origin 'http://gh.nhamoigioi.xyz' is therefore not allowed access.

[dinhnghia]

[grizzm0]

This is not related to AngularCLI. This is simply CORS built straight into your browser.

The error is telling you that your server is setup to allow "http://localhost:4200" (Access-Control-Allow-Origin is part of the response, not request). gh.nhamoigioi.xyz is therefore not allowed to access the server. You need to allow gh.nhamoigioi.xyz instead of localhost:4200 on the server side.

[ChaosJiang]

#2872 canbe help for your problem

[filipesilva]

Closing as answered by @grizzm0. ng serve itself doesn't suffer from this problem, this is a configuration issue with @dinhnghia's production server.

[shibhe]

Hi.

If you're using php as your server side, include the lines below in your .php file. it worked for me

header('Access-Control-Allow-Origin: *');
header('Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE, OPTIONS');
header('Access-Control-Allow-Headers: Origin, Content-Type, X-Auth-Token');

[dinhnghia]

thank you. but i using nodejs. i'm success 2017-10-27 14:49 GMT+07:00 Joseph <[email protected]>:

…

Hi. If you're using php as your server side, include the lines below in your .php file. it worked for me header('Access-Control-Allow-Origin: *'); header('Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE, OPTIONS'); header('Access-Control-Allow-Headers: Origin, Content-Type, X-Auth-Token'); — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7571 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANNWw3O1XnwobEQFeOtqsEqRrwAekljKks5swYrygaJpZM4PKEDe> .

-- *Võ Đình Nghĩa - Web Design & Web Developer* *Phone:* 0166 459 7661 *Email: *[email protected] *Skype: *dinhnghia.it

[fndchagas]

thank you. but i using nodejs.
i'm success

how did you solve this?

[shibhe]

How did you solve this using Node.js?

[mohd7469]

Try adding the following middleware to your NodeJS/Express app (I have added some comments for your convenience)
Add headers

app.use(function (req, res, next) {

// Website you wish to allow to connect
res.setHeader('Access-Control-Allow-Origin', 'http://localhost:8888');

// Request methods you wish to allow
res.setHeader('Access-Control-Allow-Methods', 'GET, POST, OPTIONS, PUT, PATCH, DELETE');

// Request headers you wish to allow
res.setHeader('Access-Control-Allow-Headers', 'X-Requested-With,content-type');

// Set to true if you need the website to include cookies in the requests sent
// to the API (e.g. in case you use sessions)
res.setHeader('Access-Control-Allow-Credentials', true);

// Pass to next layer of middleware
next();

});
Hope that helps!

In case you prefer something shorter, you may use a plugin called cors available for Express.js
It's simple to use, for this particular case:

var cors = require('cors');

// use it before all route definitions
app.use(cors({origin: 'http://localhost:8888'}));

[DeepikaChalana]

hello
im using angular 5 asp.net core 2.0
he error is telling you that your server is setup to allow "http://localhost:4200" (Access-Control-Allow-Origin is part of the response, not request). gh.nhamoigioi.xyz is therefore not allowed to access the server. You need to allow gh.nhamoigioi.xyz instead of localhost:4200 on the server side.

[nagipogu]

can you explain what is the issue::
Failed to load http://159.89.4.213:9000/admin/country/v1/:
No 'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'http://localhost:4200' is therefore not allowed access.

[grizzm0]

@nagipogu

The browser does a preflight OPTIONS request to the server to make sure it's allowed to fetch the data. Read more about CORS.

The server at 159.89.4.213 needs to set the following header Access-Control-Allow-Origin: http://localhost:4200.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}