strongloop / express

100%

master: 100%

LAST BUILD ON BRANCH 5.0

branch: 5.0

CHANGE BRANCH

x

Reset

• 5.0
• 3.15.3
• 3.16.0
• 3.16.1
• 3.16.10
• 3.16.2
• 3.16.3
• 3.16.4
• 3.16.5
• 3.16.6
• 3.16.7
• 3.16.8
• 3.16.9
• 3.17
• 3.17.0
• 3.17.1
• 3.17.2
• 3.17.3
• 3.17.4
• 3.17.5
• 3.17.6
• 3.17.7
• 3.17.8
• 3.18.0
• 3.18.1
• 3.18.2
• 3.18.3
• 3.18.4
• 3.18.5
• 3.18.6
• 3.19.0
• 3.19.1
• 3.19.2
• 3.20.0
• 3.20.1
• 3.20.2
• 3.20.3
• 3.21.0
• 3.21.1
• 3.21.2
• 3.x
• 4.10
• 4.10.0
• 4.10.1
• 4.10.2
• 4.10.3
• 4.10.4
• 4.10.5
• 4.10.6
• 4.10.7
• 4.10.8
• 4.11
• 4.11.0
• 4.11.1
• 4.11.2
• 4.12
• 4.12.0
• 4.12.1
• 4.12.2
• 4.12.3
• 4.12.4
• 4.13
• 4.13.0
• 4.13.1
• 4.13.2
• 4.13.3
• 4.7.3
• 4.7.4
• 4.8.0
• 4.8.1
• 4.8.2
• 4.8.3
• 4.8.4
• 4.8.5
• 4.8.6
• 4.8.7
• 4.8.8
• 4.9
• 4.9.0
• 4.9.1
• 4.9.2
• 4.9.3
• 4.9.4
• 4.9.5
• 4.9.7
• 4.9.8
• 4.9.9
• 4.x
• 5.0.0-alpha.1
• 5.0.0-alpha.2
• 5.x
• add-security-process
• appveyor
• async-route-handlers
• external-isAbsolute
• fabien-fix/app-use-mw-mount
• fce3d14
• feature/customizable-router
• fix-readme-link
• for-freenode-irc
• iterative-router
• master
• module-updates
• node_08_4
• readme-updates

Build # 2530

Build Type

Pull #2813

travis-ci

Committed by madarche

Commit Message

Security improvement: don't reveal powered-by

The first thing recommended when setting up an Express instance is to
secure it by removing its "X-Powered-By" header.

https://www.npmjs.com/package/helmet
https://blog.risingstack.com/node-js-security-checklist/
https://strongloop.com/strongblog/best-practices-for-express-in-production-part-one-security/

So let's save cycles by not setting this header in the first place.

This header is also totally useless. If some people are needing it
somewhere for a very specific usecase they can add a little custom
middleware that returns the "X-Powered-By" header again.

Pull Request Pull Request #2813: Security improvement: don't reveal powered-by

Run Details

1333 of 1335 relevant lines covered (99.85%)

555.02 hits per line