net::ERR_NETWORK_CHANGED doesn't play nice with IPv6 SLAAC
Reported by
ferrytin...@gmail.com,
Oct 16 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Have working IPv6 addresses provided by SLAAC (Stateless address autoconfiguration) 2. Load any url 3. Have Windows change the IPv6 addresses while the url is loading (hard to do because the timings) What is the expected behavior? The page loading should continue normally, and should show with all the resources present What went wrong? The full page or parts of the page fail loading with net::ERR_NETWORK_CHANGED, even though SLAAC ensures only ip addresses are removed that don't have any connections, and the page in question doesn't even have IPv6 addresses Did this work before? N/A Chrome version: 53.0.2785.143 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 Network data dump is hard to get because the timing is so difficulty, this bug affects 1 in 1000 page loads
,
Oct 17 2016
,
Oct 17 2016
Presently we don't specifically track which networks/IP addresses change and close just the sockets/DNS jobs/connect jobs specific to that network/IP address. Instead Chromium just listens for any network/IP address changes and aborts all idle sockets, DNS jobs and connect jobs. It would be a fair bit of work to implement the more specific option and the benefit might not be significant as hopefully network/IP addresses are few and far between.
,
Oct 17 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by sureshkumari@chromium.org
, Oct 17 2016