Re-enabling scraped headers (Manually) #87
Closed
Conversation
This file contains 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
Header selection is not the main topic to be developed
Configuration editor is the old property editor. Headers (custom and scraped) are handled by HeadersEditor
It was meant to be used in a different design not implemented
|
Nice |
This was
linked to
issues
Mar 29, 2023
Merged
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.
This pull request resolves #84.
A new proxy scraper using a separate data structure has been implemented (
proxy_listener.py).I have added a new button, alongside the load one, to allow the user to set custom headers before loading a particular URL.
I have rewritten the header selector. Now it is implemented as a separate component compared to the "PropertyEditor" one.
Property Editors and Headers Selectors are now different components. The latter is divided into two tabs: custom and scraped headers. Only custom headers can be included in requests made through the Burp suite, however, it is easy to move headers from the scraped to the custom tab. Moreover, only flagged custom headers will be included, making it easier to select the necessary one without losing headers that might become handy later.
Moreover, I included the change to the logic condition in the
attacker_tab.pyandgenerator_tab.pythat I also proposed as a separate pull request to themasterbranch.