Simon Bennetts

@jaywon - sent you a collaboration invite : looks like I cant assign issues to you until you accept that

@jaywon have you made any progress on this? Having looked at it I think its non trivial :/ But we still really want this functionality. Currently the requests and responses...

Yeah, we tell the browser to ignore cert errors, but I guess it doesnt ignore cert expiry. Warning the user seems like the easiest approach.

Yeah, was wondering about this myself. We'll typically get the alert details after rendering the messages in the History (or other) panel. But we should already be getting the alerts...

@Pamplemousse have you got any sites you recommend testing with? I tried https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_webstorage_local but nothing appeared when I ran the example :/

https://jsfiddle.net/Benjol/HMEVd/ failed too :/

This pull request **introduces 1 alert** when merging d747ecddcc15ee1c504a7c722920290f129c32fc into 1fdbb47854b79eff672bc6494527fd772689d6a6 - [view on LGTM.com](https://lgtm.com/projects/g/zaproxy/zap-hud/rev/pr-ded844b284caec5a38c8e668d409db8eaaf16b67) **new alerts:** * 1 for Syntax error --- *Comment posted by [LGTM.com](https://lgtm.com)*

Strictly speaking this looks like a local config issue, but no problem with trying to fix invalid or missing paths.

Agreed :)

It does say `// Generated from JavaScriptLexer.g4 by ANTLR 4.10.1` :)