Skip to content

Initialize invalid_count in UrlDecode::evaluate #1755

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

p0pr0ck5
Copy link
Contributor

The other caller of urldecode_nonstrict_inplace initialized the third param, but UrlDecode::evaluate did not.

The other caller of urldecode_nonstrict_inplace initialized
the third param, but UrlDecode::evaluate did not.
@zimmerle zimmerle self-requested a review May 3, 2018 18:19
@zimmerle
Copy link
Contributor

zimmerle commented May 3, 2018

Do you mind to describe what is the point to initialize it?

@zimmerle zimmerle self-assigned this May 3, 2018
@zimmerle zimmerle added the 3.x Related to ModSecurity version 3.x label May 3, 2018
@p0pr0ck5
Copy link
Contributor Author

p0pr0ck5 commented May 3, 2018

Good practice, since the value is unused in this context it doesn't have an impact on control flow. It's largely a quality issue (and keeping its usage in line with the other caller is good for code review purposes IMO).

@zimmerle
Copy link
Contributor

Same as #1756

@zimmerle zimmerle closed this May 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x Related to ModSecurity version 3.x
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants