[Wolfi Package Request]: nginx-mod-http-headers-more
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 443
- PR merge metrics
- No merged PRs in 30d
Description
What software would you like us to add to wolfi-os. Ideally include a URL to the project and its source.
This module allows NGINX to set, add, and clear arbitrary output and input headers. Unlike the standard add_header directive, this module works for all status codes (including 401, 404, 500, etc.) and allows for the removal of built-in headers like Server. It is a critical component for security hardening and custom header manipulation in production NGINX environments.
https://github.com/openresty/headers-more-nginx-module
which versions of the software should we include?
0.39
Add some justification for why this specific package and versions are important.
The standard NGINX add_header directive is restricted to specific HTTP status codes (2xx and 3xx) by default. The headers-more module provides critical functionality for production environments:
- Universal Header Control: It can set or clear headers for any HTTP status code, including error pages (401, 404, 5xx), which is essential for consistent security policies.
- Security Hardening: It allows for the easy removal of the Server header to prevent information leakage.
- Request Manipulation: It can modify input (request) headers, which is often necessary when NGINX is used as a reverse proxy for legacy upstream services.
- Industry Standard: This module is included by default in the OpenResty bundle and is a standard requirement for many containerized NGINX stacks.
Please check all that apply
- This package has an un-restrictive license
- The package/versions proposed are actively maintained upstream
- I am interested in adding this package to Wolfi OS myself
- I am willing to help maintain this package
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the upstream headers-more-nginx-module URL and requested version 0.39, then review existing Wolfi package conventions for NGINX modules. Done means a Wolfi package for version 0.39 is available and builds successfully with the requested module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100