Feature/proxy support #1
Open
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
1 participant
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.
Added manual proxy support (not SSL) for both Chrome and Firefox so the script could be run through Burp or Zap, e.g.:
java -jar WebGoat-Selenium.jar -host 127.0.0.1 -port 9080 -firefox -driver geckodriver -proxy -proxyHost 127.0.0.1 -proxyPort 8080 -un guest1 -pw guest1
java -jar WebGoat-Selenium.jar -host 127.0.0.1 -port 9080 -chrome -driver chromedriver -headless -proxy -proxyHost 127.0.0.1 -proxyPort 8080 -un guest1 -pw guest1
Also commented out and fixed a couple of test cases in Chrome. On the Firefox side, there is an exception not related to any of my changes where Firefox is trying to fill out a form:
"Exception in thread "main" org.openqa.selenium.ElementNotInteractableException: Element is not reachable by keyboard"