![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
http-headers-verifier
Advanced tools
Assertation framework for http-headers on top of live endpoints, Verify a pre-defined HTTP headers configurations.
Unlike some other similar projects, this is not meant to enforce best practices, instead it is meant to define policies on top of headers and enforce them. As a side effect, this means you can define specific OWASP (for example) best practices and verify them, but unlike testing for best practices, this is inteneded to verify an expected headers configuration behavior.
Relevant use cases are for example when updating nginx/caddy configuration or when moving from one web-server to another and expecting to maintain a specific set of header config.
usage: http-headers-verifier.rb [comma seperated policy names] [url] [?verbose]
$> http-headers-verifier.rb default,hs-default https://my.login.page/login verbose
Starting verification of policies default, hs-default, hs-production:
🍏 Expected Header 'Cache-Control' matched!
🍏 Expected Header 'Content-Type' matched!
🍏 Expected Header 'Vary' matched!
🍏 Expected Header 'Content-Security-Policy' matched!
🍏 Expected Header 'Expires' matched!
🍏 Expected Header 'X-Frame-Options' matched!
🍏 Expected Header 'X-XSS-Protection' matched!
🍏 Expected Header 'X-Content-Type-Options' matched!
🍏 Expected Header 'X-Whoami' matched!
🍏 Expected Header 'Strict-Transport-Security' matched!
🍏 Extra Header 'date' marked for ignore!
🍏 Extra Header 'content-length' marked for ignore!
🍏 Cookie 'AWSALB' passed verification!
🍏 Cookie 'AWSALBCORS' passed verification!
🍏 Cookie 'session' passed verification!
😎 Success !
Or in non-verbose mode:
$> http-headers-verifier.rb default,hs-default https://my.login.page/loginlogin
Starting verification of policies default, hs-default, hs-production:
🛑 Invalid cookie config 'COOKIE_NAME':
👺 Cookie not secure.
😱 Failed !
Add this line to your application's Gemfile:
gem 'http-headers-verifier'
And then execute:
$ bundle
Or install it yourself as:
$ gem install http-headers-verifier
Policy configuration is a series of YAML files, with the following naming convention:
headers-rules-*.yml
Where * is the policy named to be used in the command line.
Configuration has the following YMAL blockes:
---
headers:
cookie_attr:
ignored_headers:
headers_to_avoid:
Bug reports and pull requests are welcome on GitHub at https://github.com/AvnerCohen/http-headers-verifier. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the Http Headers Verifier
project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.
FAQs
Unknown package
We found that http-headers-verifier demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.