Specific RewriteCond makes problems in validating
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the reported RewriteCond validation result from the issue against Apache 2.2 and 2.4 behavior. Trace the validator entry point that handles this condition and compare its result with Apache; done means this valid condition is no longer reported as a false positive.
Written by the indexing model from the issue text.
Description
Hi, the following line throws a false-positive:
RewriteCond %{HTTP_HOST} ^(www\.u|u-|www\.u-|you|www\.you|you-|www\.you-|uni|www\.uni)book\.at$ [NC]
RewriteRule ^(.*)$ https://mywebsite.com/$1 [R=301,L]
In real this line doesn't fail in Apache 2.2 and 2.4
- Dominant language
- PHP
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
coollabsio/coolify#11927 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100