HTTP Module: Keep scanner.config immutable during scans #245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Scanner.config struct is a configuration for all instances of Scanner. Scanner.Scan() is called concurrently by multiple worker goroutines; while Scanner is dereferenced before the call, the config struct is a pointer, and so modifications to it will affect all other running scans done with that scanner.
Make sure we treat it as immutable during anything invoked by Scanner.Scan() in the http module.
Add a description of your changes here.
How to Test
Add brief instructions on how to test your changes.
Notes & Caveats
This bug should only manifest itself if
--retry-https
is true, and--use-https
is false.jIssue Tracking
Add a link to the relevant GitHub issue(s) if the pull request resolves it.