Remove noCache from "mainline" Helmet

[EvanHahn]

In an effort to focus this project's scope, I'm trying to make sure that Helmet only focuses on HTTP response headers that are strictly related to security. While nocache is useful, it's not strictly security-related in my eyes, so I'm removing it.

This functionality isn't going away. It's just moving to a separate module, nocache. You can find it on npm and on GitHub.

Instead of this:

const helmet = require('helmet')
// ...
app.use(helmet.noCache())

You'll do this:

const noCache = require('nocache')
// ...
app.use(noCache())

This is a breaking change that will be part of Helmet 4.

[unbalanced]

Hey, can you refer me to information on why it was removed from the "default" settings and will be removed in Helmet 4?

Thanks

[EvanHahn]

In an effort to focus this project's scope, I'm trying to make sure that Helmet only focuses on HTTP response headers that are strictly related to security. While nocache is useful, it's not strictly security-related in my eyes, so I'm removing it.

This functionality isn't going away. It's just moving to a separate module, nocache.

[JEstradaDev]

hi!! could you add the link for nocache module or new documentation?? please

thanks.

[EvanHahn]

@JEstradaDev Good idea. I've added more information to the description of this issue.

[EvanHahn]

This was done in ca483bd and merged into the upcoming v4 branch (see #197).