Simon Bennetts

I dont think we need a UI right now. It could be a panel in the Options, but def not a priority for me.

Having worked at Mozilla I'm pretty sure they wont mind either way 😉 But I'm all for reducing the noise from browser calls home..

Its worth nothing that the OpenAPI add-on does not support importing an API definition using an authenticated user at all, not just via the AF plan 😁

@javixeneize have you tried using tags? you can automatically tag requests based on regexes, and then filter on those tags in the History table. Also related to #4000

https://github.com/zaproxy/zap-core-help/wiki/HelpStartConceptsTags

Non alpha components without any API support: - [ ] Forced Browse #2849 - [ ] Fuzzing #1689 - [x] Websockets (zaproxy/zap-extensions#1397) - [ ] Applications - [x] Replacer -...

There should also be options to stop the ZAP scan if the server starts returning too many (for example) 5xx codes, or too many auth failures.

I thought we were waiting for you to change to use LOG or LOGGER? 😉

I'd recommend updating VueJs first. That will need to work before we can merge the changes, but then the restructuring can be performed over multiple PRs (if that works better)....

Pick a wiki page and have a look on the right hand side - you should see `Clone this wiki locally` - you can then update it and submit PRs...