You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, to make intercepts work properly, you have to exclude these two URLs. When you do, you still seem them all the time, presumably because HUD forces HTTPS (which seems weird to me).
So, to REALLY get ZAP to stop logging these URLs, you have to also add:
It sounds like ZAP is not upgrading the http AJAX calls. Do you see redirects in the responses?
Is WebGoat not following the redirects?
If you can explain how it works then we can look at fixing it.
Although right now we dont actually have anyone focussing on HUD development :(
This is related to issue #585 I believe.
When you launch ZAP w/FireFox and HUD you see lots of automatic AJAX requests to:
http://localhost:8080/WebGoat/service/lessoninfo.mvc
http://localhost:8080/WebGoat/service/lessonmenu.mvc.*
So, to make intercepts work properly, you have to exclude these two URLs. When you do, you still seem them all the time, presumably because HUD forces HTTPS (which seems weird to me).
So, to REALLY get ZAP to stop logging these URLs, you have to also add:
https://localhost:8080/WebGoat/service/lessoninfo.mvc
https://localhost:8080/WebGoat/service/lessonmenu.mvc.*
Which is NOT intuitive at all. And after you do this, other things break. Specifically:
When you add: https://localhost:8080/WebGoat/service/lessoninfo.mvc - You stop seeing the lesson stages for each lesson. You either see blank, or only stage 1, even if there are like 5, 6, 10 stages to a lessons.
When you add: https://localhost:8080/WebGoat/service/lessonmenu.mvc - You see a spinner forever where the lesson menu should be.
As ZAP and WebGoat are BOTH from OWASP, seems like we should figure out how to make them work well together well with the HUD.
First off, WHY does it force HTTPS? Doesn't seem like it should need to do that. If we stopped doing that, both these issues might just 'go away'.
The text was updated successfully, but these errors were encountered: