openresty / openresty/headers-more-nginx-module
does more_headers_set work with 301 status code
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 236
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 2
Description
I tried more_set_headers "X-foo: foo";
it seems working for status 200 HTTP response. If the status is 301, the header X-foo is not added.
Contributor guide
No contributing guide indexed for this repository
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
No source file or test is named in the report. Reproduce the behavior with an NGINX HTTP configuration for both 200 and 301 responses, then locate the module's header-handling entry point; done when X-foo is present for 301 responses and regression coverage verifies both statuses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, nginx
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100