owasp-modsecurity / owasp-modsecurity/ModSecurity
Sorted collections
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
For some collections (ARGS, REQUEST_COOKIES), it may be necessary to have them sorted in order to concatenate them in an intelligent way (i.e. concatenated all ARGS named "a" without others in the middle). Think about HTTP parameter pollution...
SORTED_MATCHED_VARS should be sufficient to handle sorting of any collection with an intermediate rule.
The sorting should be alphabetically (case-insensitive for the name) but keep the entries with the same name in the original order.
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
Locate SORTED_MATCHED_VARS and the collection-handling entry points for ARGS and REQUEST_COOKIES. First trace how collection entries are represented and concatenated, then determine how an intermediate sorting rule would preserve original order for case-insensitive name ties. Done means the supported collections can be sorted alphabetically without changing the order of entries with the same name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100