Skip to content

fix: move rule's phase 950100 to 3#3941

Merged
airween merged 2 commits into
coreruleset:v3.3/devfrom
airween:v3.3/correct_phase_950100
Nov 18, 2024
Merged

fix: move rule's phase 950100 to 3#3941
airween merged 2 commits into
coreruleset:v3.3/devfrom
airween:v3.3/correct_phase_950100

Conversation

@airween
Copy link
Copy Markdown
Contributor

@airween airween commented Nov 18, 2024

Rule 950100 in branch v3.3 has the phase:4, but it could be in phase:3.

There is an open issue about this problem: #3936, where the reporter describes the details. Also he mentioned my previously PR #1941, but it made for v3.4 (which wasn't released) and we haven't back-ported anything.

This PR only moves one rule's phase, but there are many other rules where we can make this step - the question is do we want to do this or not.

@fzipi
Copy link
Copy Markdown
Member

fzipi commented Nov 18, 2024

I would say yes, we want to move all the rules than can be moved to phase 3 if the condition is applying on response headers only.

@airween airween merged commit a90007b into coreruleset:v3.3/dev Nov 18, 2024
@airween
Copy link
Copy Markdown
Contributor Author

airween commented Nov 18, 2024

I would say yes, we want to move all the rules than can be moved to phase 3 if the condition is applying on response headers only.

Thanks, I merged this one into v3.3/dev, I think we merge everything from that into v3.3/main before next release.

I'll open a new PR soon to fix the other phases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants