openresty / openresty/lua-nginx-module
order of run phase when slicing is on?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
in openresty 1.15.x version , when slicing is on (like: slice 100m ;) for origin content (big than 100 m: 1gb) with wget, in first request range[0-100] openresty phases run order is correct and start from Rewrite/Access phase, but in seccond request range [100-200 ] openresty phase start from Content_phase (balancer_by_lua), but i need ctx that set in older phase and previous request range [0-100] context is cleand (maybe for internal redirect), and in this phase i cant get some data because not access to connect redis or dns resolver.
in old version like 1.11.x or 1.13.x every thing is correct , but in 1.15.x version start from Content_phase and is a problem
What will i do؟
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. Reproduce the reported 100m slicing case against a 1gb origin with wget, comparing OpenResty 1.15.x with 1.11.x or 1.13.x and focusing on balancer_by_lua, request phases, and ctx across ranges. Done means establishing whether the phase-order difference is a regression or expected behavior and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100