Header exposing npm module name and store used.
See original GitHub issueThe below lines in file apicache.js are exposing couple of critical information to the www.
- It is exposing that apicache is being used at server.
- If redis is used with it, It is exposing that redis is being used at server.
'apicache-store': globalOptions.redisClient ? 'redis' : 'memory', 'apicache-version': pkg.version
These headers should be removed. If not, atleast there should be a production check before assigning any additional module specific headers. Something like: `if (process.env.NODE_ENV !== “production”) {
}`
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
package.json - npm Docs
json which is a map of command name to local file name. When this package is installed globally, that file will be either...
Read more >Import from subfolder of npm package - Stack Overflow
I create subfolders with ES6 source code in the root of the project and publish those dirs to NPM, but I guess this...
Read more >Requiring modules in Node.js: Everything you need to know
There is nothing special about require . It's an object that acts mainly as a function that takes a module name or path...
Read more >Access-Control-Expose-Headers - HTTP - MDN Web Docs
The Access-Control-Expose-Headers response header allows a server to indicate which response headers should be made available to scripts ...
Read more >How To Work with Files using the fs Module in Node.js
The name is short for “file system,” and the module contains all the functions you need to read, write, and delete files on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Got it - will implement a test and (at least) leave headers off on
NODE_ENV === 'production'
Awesome, Thanks! 😃