Welcome! Log In Create A New Profile

Advanced

Uniquely identify the client

Posted by ric0 
Uniquely identify the client
November 08, 2017 10:02AM
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.



Edited 1 time(s). Last edit at 11/08/2017 10:12AM by ric0.
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 99
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready