-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
Sites upgraded to https fail if 'only in scope' switched on #316
Comments
Great find! More usability tests! |
Got the same error problem.
I disable the option 'Enable the HUD only for URLs that are in scope' and everything work again. ZAP v.2.8.0 |
psiinon
added a commit
to psiinon/zap-hud
that referenced
this issue
Nov 21, 2019
psiinon
added a commit
to psiinon/zap-hud
that referenced
this issue
Nov 22, 2019
psiinon
added a commit
to psiinon/zap-hud
that referenced
this issue
Nov 22, 2019
Fixes zaproxy#316 Signed-off-by: Simon Bennetts <[email protected]>
psiinon
added a commit
to psiinon/zap-hud
that referenced
this issue
Nov 22, 2019
Fixes zaproxy#316 Signed-off-by: Simon Bennetts <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Start using the HUD with an HTTP based site, but dont add it to the scope. The HUD will upgrade it to HTTPS.
Turn on the 'Enable the HUD only for URLs that are in scope' option.
The site will then fail with "Unrecognized SSL message, plaintext connection?" errors.
This is pretty confusing, especially for newcomers.
(Thanks mum: https://twitter.com/psiinon/status/1077890840142450689 ;)
The text was updated successfully, but these errors were encountered: