This is a conenct/express middleware for evercookie. For more information, visit https://github.com/samyk/evercookie or https://github.com/senchalabs/connect
This middleware port original PHP script to Connect/Express JS
npm install --save evercookie
Evercookie backend middleware needs cookie, thus
express.cookieParser() middleware must come before Evercookie backend middleware.
In addition, express server must serve front end assets, such as index.html and evercookie.js as well.
var express = require'express';var evercookie = require'evercookie';var app = express;appuseexpresscookieParser;appuseevercookiebackend;appuseexpresscookieParser;appuseexpressstatic__dirname + '/public'; // be careful, you may want to use path.join instead!
Customized settings can be used, but up to this moment, it makes no sense to change the dafault one,
as all these values are hardcoded in (frontend)
//...appuseevercookiebackendpngCookieName: 'evercookie_png'etagCookieName: 'evercookie_etag'cacheCookieName: 'evercookie_cache'pngPath: '/evercookie_png.php'etagPath: '/evercookie_etag.php'cachePath: '/evercookie_cache.php';//...
The MIT License (MIT) Copyright (c) 2013 TruongSinh Tran-Nguyen
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.