Fix/attack cookies option - #48
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixes the --cookies CLI/API option being silently ignored by the attack service, and unifies how cookies are passed across all services (session jar in the HTTPClient constructor instead of mixed per-request kwargs).
Fix:
Unification (analyze + scrape services):
Tests: test_scrape_service.py updated to expect cookies=None in the HTTPClient construction assertion.
Related Issue
N/A — discovered during live validation against DVWA (authenticated scan redirected to login because cookies were never sent).
Type of Change
Checklist