thc202
thc202
Didn't review the changes yet, needs rebase to pick the release done in the meantime.
The message `See the Automation tab's Output panel for details.` needs to be tweaked.
That's a side effect of not doing this way https://github.com/zaproxy/zap-extensions/pull/5861#discussion_r1935882649
Would be good to add a meaningful commit message.
Thank you all!
That's a news item.
IMHO this is a workaround not a fix, the offending endpoints (not just about `alertCountsByRisk`) should be changed to return properly formed data. Otherwise why is it just "sanitizing" spaces...
The `XMLStringUtil.escapeControlChrs` is used for the values which can contain spaces and pretty much any other character. As mentioned in the previous comment this should be fixed in the endpoints,...
The problem is not in `XMLStringUtil` nor `ApiResponseSet` but `AlertAPI` which is creating an invalid XML `ApiResponse`, that's where the fix should be.
Is the database add-on installed too?