thc202
thc202
Good that works but ZAP is/was running with correct arch. In any case, I guess we could apply that workaround when building the arm64 dist…
They use the same source of information.
That's a different issue: #6162.
Browsers are no longer warning.
I just followed the steps you provided (which are the same as #8877) and I see both individual alerts as the whole group being marked as False Positive: Maybe you/OP...
There's no need to try anything, the steps provided allow to reproduce the issue reported.
There's already a PR adding this.
Why the rush to raise PRs?
This is not a good first issue, it has no clear outcomes defined yet. What are your interests? [ZAP Developer Group](https://groups.google.com/g/zaproxy-develop) is a better place to talk about this. (Note...
You need to keep binary compatibility, e.g. add a new constructor instead of changing that one.