Simon Bennetts

Updated based on comments received, and fixed the minor problem that the persistent callback URLs didnt actually work 😛

Should have fixed the lgtm comment..

That comment will do - the more people who ping us on the status of an issue the more we appreciate how important those issues are. You can also vote...

The latest reports are detailed on https://www.zaproxy.org/docs/desktop/addons/report-generation/templates/

The report add-on help is available online at https://www.zaproxy.org/docs/desktop/addons/report-generation/ Each report is documented in links off https://www.zaproxy.org/docs/desktop/addons/report-generation/templates/ Have a look at the report samples and see which ones report alerts...

I can see why this would be useful ... but I'm afraid I dont think we should implement it in the full scan. I dont think everyone would want this...

Interestingly enough I can reproduce this on my Mac for some directories but not others. I'm sure its a MacOS configuration issue not a ZAP problem, but I'm not an...

I'm not aware of any change we've made to ZAP which could have affected this, so I still think its a MacOS configuration issue. Dont forget that when you run...

> ZAP provides its own Java binary: `/Applications/OWASP ZAP.app/Contents/Home/bin/java` > > If that one's being used, it's that process which should query MacOS for access permissions to ~/Documents. And since...

Is it really a bug in ZAP or just missing / incomplete documentation? As far as I can tell its Mac's being a pain, not something we can actually fix...