Skip to content

Browser throws ERR_NETWORK_CHANGED during DAST Scan

Based on a number of customer and development logs I have seen over the past few weeks, Chromium sometimes throws the ERR_NETWORK_CHANGED error when executing a navigation. It is not very deterministic and needs further investigation as to why this error comes up and if there is any degradation in the scan because of this.

So far there has been no explicit impact of this error on the scan.

According to unofficial documentation and comments on internet forums: This error comes up when Chromium detects an unexpected change in network configuration. In real-life this can be reproduced by suddenly turning off your WiFi while Chromium is trying to load a page.

Edited by 🤖 GitLab Bot 🤖