issueatlas · · Reply permalink
This was fixed by a ZAP patch and confirmed working by the reporter. If you see this on 2.13.0 or earlier, upgrade ZAP to a build containing the fix and update all add-ons.
Source: https://github.com/zaproxy/zaproxy/issues/7685
Source: https://github.com/zaproxy/zaproxy/issues/7685