我已经在Heroku中部署(托管)了cors-anywhere,但我不知道如何对其进行自定义。例如,我想在白名单中添加一个站点链接。我从这个链接获取数据:http://fmon.asti.dost.gov.ph/dataloc.php?param=rv&dfrm=null&dto=null&numloc=1&data24=1&locs[]=711
我该怎么做呢?我尝试过触摸server.js文件:
// Listen on a specific host via the HOST environment variable
var host = process.env.HOST || '0.0.0.0';
// Listen on a specific port via the PORT environment variable
//var port = process.env.PORT || 443;
var port = process.env.PORT || 8080;
// Grab the blacklist from the command-line so that we can update the blacklist without deploying
// again. CORS Anywhere is open by design, and this blacklist is not used, except for countering
// immediate abuse (e.g. denial of service). If you want to block all origins except for some,
// use originWhitelist instead.
var originBlacklist = parseEnvList(process.env.CORSANYWHERE_BLACKLIST);
//var originWhitelist = ['http://fmon.asti.dost.gov.ph/dataloc.php','https://fmon.asti.dost.gov.ph/dataloc.php','http://fmon.asti.dost.gov.ph','https://fmon.asti.dost.gov.ph'];
var originWhitelist = parseEnvList(process.env.CORSANYWHERE_WHITELIST);
function parseEnvList(env) {
if (!env) {
return [];
}
return env.split(',');
}
// Set up rate-limiting to avoid abuse of the public CORS Anywhere server.
var checkRateLimit = require('./lib/rate-limit')(process.env.CORSANYWHERE_RATELIMIT);
var cors_proxy = require('./lib/cors-anywhere');
cors_proxy.createServer({
originBlacklist: originBlacklist,
originWhitelist: originWhitelist,
requireHeader: ['origin', 'x-requested-with'],
checkRateLimit: checkRateLimit,
removeHeaders: [
'cookie',
'cookie2',
// Strip Heroku-specific headers
'x-heroku-queue-wait-time',
'x-heroku-queue-depth',
'x-heroku-dynos-in-use',
'x-request-start',
],
redirectSameOrigin: true,
httpProxyOptions: {
// Do not add X-Forwarded-For, etc. headers, because Heroku already adds it.
xfwd: false,
},
}).listen(port, host, function() {
console.log('Running CORS Anywhere on ' + host + ':' + port);
});但是当我访问数据并查看控制台日志时,它返回一个403错误,这是被禁止的。
发布于 2017-06-20 13:30:55
注意:当你说自己托管的CORS时,它只适用于你的站点代理。您服务器上的CORS设置是针对您的,而不是针对您提到的站点列表。他们将有自己的CORS过滤器设置。
403实际上是指被禁止的资源,而不是CORS问题。Cors问题将如下所示:
否请求的资源上存在'Access-Control-Allow-Origin‘标头。因此不允许访问源'yourUrl‘。该响应具有HTTP状态代码400
对于cors-anywhere,白名单代码非常简单,如下所述:
// Listen on a specific host via the HOST environment variable
var host = process.env.HOST || '0.0.0.0';
// Listen on a specific port via the PORT environment variable
var port = process.env.PORT || 8080;
var cors_proxy = require('cors-anywhere');
cors_proxy.createServer({
originWhitelist: ['http://fmon.asti.dost.gov.ph'], // Allow all origins
requireHeader: ['origin', 'x-requested-with'],
removeHeaders: ['cookie', 'cookie2']
}).listen(port, host, function() {
console.log('Running CORS Anywhere on ' + host + ':' + port);
});理想情况下,当您的应用程序在某个地方调用它时,这应该可以为您工作。
如果您在从应用程序访问此URL时获得403,请确保您提到的URL受到保护,并且在请求它之前必须进行适当的身份验证。
发布于 2021-01-15 18:51:58
我花了3天的时间寻找原因,在一些网站上得到了403错误,并意识到问题可能是他们不能接受来自不同于他们的“来源”的请求。我只是试着在代理服务器上删除这些头文件,一切都正常!
removeHeaders: ['origin', 'referer']https://stackoverflow.com/questions/44644471
复制相似问题