blocks|key|340557|text|如果您运行在诸如NGiNX之类的代理或其他代理之后，那么只有这样才应该检查'x-forwarded-for'|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|340558|var+ip+=+req.headers['x-forwarded-for']+%7C%7C+req.socket.remoteAddress+|code-block|syntax|javascript|340559|如果代理不是“您的”，我不会信任'x-forwarded-for'头，因为它可能被欺骗。|340560|entityMap^0|11|H|0|0|G|H|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

If you are running behind a proxy like NGiNX or what have you, only then you should check for <code>'x-forwarded-for'</code>:
<pre><code>var ip = req.headers['x-forwarded-for'] || req.socket.remoteAddress 
</code></pre>
If the proxy isn't 'yours', I wouldn't trust the <code>'x-forwarded-for'</code> header, because it can be spoofed.

blocks|key|340603|text|根据Express+behind+proxies的说法，如果您正确配置了req.ip，则trust+proxy会考虑反向代理。因此，它比从网络层获得的、不知道代理的req.connection.remoteAddress协议要好。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|340604|entityMap|0|LINK|mutability|MUTABLE|url|https://expressjs.com/en/guide/behind-proxies.html^0|10|6|18|B|2A|S|2|M|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

According to <a href="https://expressjs.com/en/guide/behind-proxies.html" rel="nofollow noreferrer">Express behind proxies</a>, <code>req.ip</code> has taken into account reverse proxy if you have configured <code>trust proxy</code> properly. Therefore it's better than <code>req.connection.remoteAddress</code> which is obtained from network layer and unaware of proxy.

blocks|key|556654|text|这对我来说比其他方法更有效。我的网站是CloudFlare的后盾，它似乎需要cf-connecting-ip。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|556655|req.headers['cf-connecting-ip']+%7C%7C+req.headers['x-forwarded-for']+%7C%7C+req.connection.remoteAddress|code-block|syntax|javascript|556656|没有测试Express+behind+proxies，因为它没有说明有关此cf-connecting-ip标头的任何内容。|556657|entityMap|0|LINK|mutability|MUTABLE|url|https://expressjs.com/en/guide/behind-proxies.html^0|12|G|0|0|11|G|4|M|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

This worked for me better than the rest. My sites are behind CloudFlare and it seemed to require <code>cf-connecting-ip</code>. 

<pre><code>req.headers['cf-connecting-ip'] || req.headers['x-forwarded-for'] || req.connection.remoteAddress
</code></pre>

Didn't test <a href="https://expressjs.com/en/guide/behind-proxies.html" rel="nofollow noreferrer">Express behind proxies</a> as it didn't say anything about this <code>cf-connecting-ip</code> header.

blocks|key|556698|text|var+ip+=+req.connection.remoteAddress；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556699|ip+=+ip.split(':')3；|556700|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

var ip = req.connection.remoteAddress;

ip = ip.split(':')[3];

blocks|key|340735|text|headers对象具有您需要的所有内容，只需执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340736|var+ip+=+req.headers['x-forwarded-for'].split(',')[0];|code-block|syntax|javascript|340737|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The headers object has everything you need, just do this: 

<pre><code>var ip = req.headers['x-forwarded-for'].split(',')[0];
</code></pre>

blocks|key|340804|text|我为此写了一个包。您可以将其用作express中间件。我的包发布在这里：https://www.npmjs.com/package/express-ip|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|340805|您可以使用以下命令安装该模块|340806|npm+i+express-ip|code-block|syntax|javascript|340807|用法|340808|const+express+=+require('express');
const+app+=+express();
const+expressip+=+require('express-ip');
app.use(expressip().getIpInfoMiddleware);

app.get('/',+function+(req,+res)+{
++++console.log(req.ipInfo);
});|340809|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/express-ip^0|10|14|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

I wrote a package for that purpose. You can use it as express middleware. My package is published here: <a href="https://www.npmjs.com/package/express-ip" rel="nofollow noreferrer">https://www.npmjs.com/package/express-ip</a> 

You can install the module using 

<pre><code>npm i express-ip
</code></pre>

Usage

<pre><code>const express = require('express');
const app = express();
const expressip = require('express-ip');
app.use(expressip().getIpInfoMiddleware);

app.get('/', function (req, res) {
 console.log(req.ipInfo);
});
</code></pre>

blocks|key|340903|text|我知道这个问题已经得到了回答，但以下是我的问题是如何工作的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340904|let+ip+=+req.connection.remoteAddress.split(`:`).pop();|code-block|syntax|javascript|340905|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I know this question has been answered, but here's how I got mine to work.

<pre><code>let ip = req.connection.remoteAddress.split(`:`).pop();
</code></pre>

blocks|key|556925|text|这只是this+answer的附加信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|556926|如果您使用的是nginx，您可以将proxy_set_header++X-Real-IP++$remote_addr;添加到站点的位置块中。例如，/etc/nginx/sites-available/www.example.com。这是一个服务器块示例。|style|CODE|556927|server+{
++++listen+80;
++++listen+[::]:80;

++++server_name+example.com+www.example.com;

++++location+/+{
++++++++proxy_set_header++X-Real-IP++$remote_addr;
++++++++proxy_pass+http://127.0.1.1:3080;
++++++++proxy_http_version+1.1;
++++++++proxy_set_header+Upgrade+$http_upgrade;
++++++++proxy_set_header+Connection+'upgrade';
++++++++proxy_set_header+Host+$host;
++++++++proxy_cache_bypass+$http_upgrade;
++++}
}|code-block|syntax|javascript|556928|重新启动nginx后，您将能够使用req.headers['x-real-ip']+%7C%7C+req.connection.remoteAddress;访问node/express应用程序路由中的ip|556929|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/18481747/11312528^0|3|B|0|0|7|5|H|16|21|16|0|0|4|5|H|1L|24|4|29|7|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]|$A|13|B|14|F|G]|$A|15|B|16|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|17|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|18|8|@$A|19|B|1A|F|G]|$A|1B|B|1C|F|G]|$A|1D|B|1E|F|G]|$A|1F|B|1G|F|G]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

This is just additional information for <a href="https://stackoverflow.com/a/18481747/11312528">this answer</a>. 

If you are using <code>nginx</code>, you would add <code>proxy_set_header X-Real-IP $remote_addr;</code> to the location block for the site. <code>/etc/nginx/sites-available/www.example.com</code> for example. Here is a example server block.

<pre><code>server {
 listen 80;
 listen [::]:80;

 server_name example.com www.example.com;

 location / {
 proxy_set_header X-Real-IP $remote_addr;
 proxy_pass http://127.0.1.1:3080;
 proxy_http_version 1.1;
 proxy_set_header Upgrade $http_upgrade;
 proxy_set_header Connection 'upgrade';
 proxy_set_header Host $host;
 proxy_cache_bypass $http_upgrade;
 }
}
</code></pre>

After restarting <code>nginx</code>, you will be able to access the ip in your <code>node</code>/<code>express</code> application routes with <code>req.headers['x-real-ip'] || req.connection.remoteAddress;</code>

blocks|key|556972|text|支持and+flare、nginx和x-real-ip|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556973|var+user_ip;

++++if(req.headers['cf-connecting-ip']+&&+req.headers['cf-connecting-ip'].split(',+').length)+{
++++++let+first+=+req.headers['cf-connecting-ip'].split(',+');
++++++user_ip+=+first[0];
++++}+else+{
++++++let+user_ip+=+req.headers['x-forwarded-for']+%7C%7C+req.headers['x-real-ip']+%7C%7C+req.connection.remoteAddress+%7C%7C+req.socket.remoteAddress+%7C%7C+req.connection.socket.remoteAddress;
++++}|code-block|syntax|javascript|556974|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

With could-flare, nginx and x-real-ip support

<pre><code>var user_ip;

 if(req.headers['cf-connecting-ip'] &amp;&amp; req.headers['cf-connecting-ip'].split(', ').length) {
 let first = req.headers['cf-connecting-ip'].split(', ');
 user_ip = first[0];
 } else {
 let user_ip = req.headers['x-forwarded-for'] || req.headers['x-real-ip'] || req.connection.remoteAddress || req.socket.remoteAddress || req.connection.socket.remoteAddress;
 }
</code></pre>

blocks|key|341080|text|将所有witk+@kakopappa解决方案与客户端ip地址的morgan日志记录放在一起：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|341081|morgan.token('client_ip',+function+getId(req)+{
++++return+req.client_ip
});
const+LOG_OUT+=+':remote-addr+-+:remote-user+[:date[clf]]+":method+:url+HTTP/:http-version"+:status+:res[content-length]+":referrer"+":user-agent"+:client_ip'
self.app.use(morgan(LOG_OUT,+{
++++skip:+function(req,+res)+{+//+custom+logging:+filter+status+codes
++++++++return+res.statusCode+<+self._options.logging.statusCode;
++++}
}));

//+could-flare,+nginx+and+x-real-ip+support
var+getIpInfoMiddleware+=+function(req,+res,+next)+{
++++var+client_ip;
++++if+(req.headers['cf-connecting-ip']+&&+req.headers['cf-connecting-ip'].split(',+').length)+{
++++++++var+first+=+req.headers['cf-connecting-ip'].split(',+');
++++++++client_ip+=+first[0];
++++}+else+{
++++++++client_ip+=+req.headers['x-forwarded-for']+%7C%7C+req.headers['x-real-ip']+%7C%7C+req.connection.remoteAddress+%7C%7C+req.socket.remoteAddress+%7C%7C+req.connection.socket.remoteAddress;
++++}
++++req.client_ip+=+client_ip;
++++next();
};
self.app.use(getIpInfoMiddleware);|code-block|syntax|javascript|341082|entityMap^0|V|6|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Putting all together witk @kakopappa solution plus <code>morgan</code> logging of the client ip address:

<pre><code>morgan.token('client_ip', function getId(req) {
 return req.client_ip
});
const LOG_OUT = ':remote-addr - :remote-user [:date[clf]] ":method :url HTTP/:http-version" :status :res[content-length] ":referrer" ":user-agent" :client_ip'
self.app.use(morgan(LOG_OUT, {
 skip: function(req, res) { // custom logging: filter status codes
 return res.statusCode &lt; self._options.logging.statusCode;
 }
}));

// could-flare, nginx and x-real-ip support
var getIpInfoMiddleware = function(req, res, next) {
 var client_ip;
 if (req.headers['cf-connecting-ip'] &amp;&amp; req.headers['cf-connecting-ip'].split(', ').length) {
 var first = req.headers['cf-connecting-ip'].split(', ');
 client_ip = first[0];
 } else {
 client_ip = req.headers['x-forwarded-for'] || req.headers['x-real-ip'] || req.connection.remoteAddress || req.socket.remoteAddress || req.connection.socket.remoteAddress;
 }
 req.client_ip = client_ip;
 next();
};
self.app.use(getIpInfoMiddleware);
</code></pre>

I don't completely understand how I should get a remote user IP address.

Let's say I have a simple request route such as:

<pre><code>app.get(/, function (req, res){
 var forwardedIpsStr = req.header('x-forwarded-for');
 var IP = '';

 if (forwardedIpsStr) {
 IP = forwardedIps = forwardedIpsStr.split(',')[0]; 
 }
});
</code></pre>

Is the above approach correct to get the real user IP address or is there a better way?
And what about proxies?

Express.js: how to get remote client address

中间件

服务器

路由

我不完全理解如何获取远程用户的IP地址。假设我有一个简单的请求路由，如下所示：app.get(/, function (req, res){   var forwardedIpsStr = req.header('x-forwarded-for');   var IP = '';   if (forwardedIpsS...

问Express.js:如何获取远程客户端地址
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Express.js:如何获取远程客户端地址EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Express.js:如何获取远程客户端地址
EN