litespeedtech / litespeedtech/openlitespeed
RewriteRule with [next] flag?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 233
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
I was fiddling just a bit and discovered the `[next]` rewrite flag isn't working. I'm not positive, but I'm wondering if that could be caused by the `ne` check here that comes before the `next` check? https://github.com/litespeedtech/openlitespeed/blob/2506fbc8ae1fe74d37cf5b7d639bc182b66daf0e/src/http/rewriterule.cpp#L842
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
Start in src/http/rewriterule.cpp around line 842, where the issue points to the [ne] and [next] checks. Reproduce a rewrite rule using the [next] flag, then inspect whether the check ordering explains the failure. Done means [next] behaves as expected and the relevant behavior is covered by a reproducible verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100