Mozilla states that it has learned several lessons from the issue.
All HTTP/3 connections go through the networking stack Necko, but Rust components use a library called viaduct to call Necko. Mozilla investigated the issue in more detail after the most pressing issue had been taken care of. The HTTP/3 setting at the cloud provider was configured with the automatic value. HTTP/3 was disabled by Mozilla and users could finally use Firefox again to connect to services. Settings were not changed in inspection, but engineers noticed that the Telemetry service was serving HTTP/3 connections, which it had not done before. The organization uses the infrastructure of several providers for services such as crash reporting, telemetry, updating or certificate management. Mozilla suspected that the issue could have been caused by a recent "invisible" configuration change by one of the cloud providers that it uses for load balancing. Engineers looked at recent changes or updates, but did not find any that could cause the issue that users experienced. Mozilla engineers discovered that a network request was causing the hangs for Firefox users.
0 kommentar(er)
