I just tested this on my local machine.
748742 [ZAP-Scanner-0] INFO Â org.parosproxy.paros.core.scanner.HostProcess - completed host/plugin https://www.grunge.com | SqlInjectionSqLiteScanRule in 0.8s with 19 message(s) sent and 0 alert(s) raised.
748742 [ZAP-Scanner-0] INFO Â org.parosproxy.paros.core.scanner.HostProcess - start host https://www.grunge.com | DomXssScanRule strength MEDIUM threshold MEDIUM
752658 [Thread-453] INFO Â org.zaproxy.zap.extension.domxss.DomXssScanRule - Reaper thread starting
1002667 [ZAP-IO-Server-1-16] INFO Â org.apache.hc.client5.http.impl.classic.ZapHttpRequestRetryExec - Recoverable I/O exception (org.apache.hc.core5.http.NoHttpResponseException) caught when processing request to {s}->https://a.audrte.com:443
Owasp Zap thinks for a long time at this step, but eventually it successfully completes the scan.
On the local machine, I run Owasp Zap in a container and the application outside the container.
In the production environment, the application runs together with Owasp Zap in the same container.
At the same time, this container has limitations on memory and cpu.
From the log you can see that there is some kind of timeout happening after 30 seconds. But with the same settings, there is no timeout locally.
Could this be the reason for limiting container resources?
Or maybe you can recommend some parameter at startup that will help either increase the timeout or provide more information about why such an error occurs in the container.
Thanks for the help.