I'm developing a web app using Node.js and I came across the following npm package that does more or less what I am looking for. That is to somehow uniquely identify the client that connects to my server.
https://github.com/yusukeshibata/express-fingerprint
This work great during local development and on the staging environment though in production I always use nginx and I'm wondering if is even possible to achieve the same functionality as those offered by the express-fingerprint package.
The package for instance uses the following sources to create a fingerprint of the connected client:
User Agent
HTTP_ACCEPT Headers
GEO-ip
Then create a fingerprint of the above and hash the result.
The only out of the box solution for nginx I found is the geoip functionality:
http://nginx.org/en/docs/http/ngx_http_geoip_module.html
Is there anything else that could cover headers and user agent ($http_user_agent??) like express-fingerprint? Let alone hashing them on nginx to lessen the load of my server.
Thank you.
https://github.com/yusukeshibata/express-fingerprint
This work great during local development and on the staging environment though in production I always use nginx and I'm wondering if is even possible to achieve the same functionality as those offered by the express-fingerprint package.
The package for instance uses the following sources to create a fingerprint of the connected client:
User Agent
HTTP_ACCEPT Headers
GEO-ip
Then create a fingerprint of the above and hash the result.
The only out of the box solution for nginx I found is the geoip functionality:
http://nginx.org/en/docs/http/ngx_http_geoip_module.html
Is there anything else that could cover headers and user agent ($http_user_agent??) like express-fingerprint? Let alone hashing them on nginx to lessen the load of my server.
Thank you.