Search results

HTTP error responses implementations inconsistent with spec

Status: Open.

#191 In w3c/network-error-logging;

· tunetheweb opened on Aug 28, 2025

Deal with fetchParams

Status: Open.

#188 In w3c/network-error-logging;

· miketaylr opened on Feb 17, 2025

Should some Predefined network error types map directly to fetch error states?

Status: Open.

#185 In w3c/network-error-logging;

· miketaylr opened on Feb 7, 2025

Map NEL phases to fetch

Status: Open.

#184 In w3c/network-error-logging;

· miketaylr opened on Feb 7, 2025

Redefine report delivery in terms of Fetch

Status: Open.

#183 In w3c/network-error-logging;

· miketaylr opened on Feb 7, 2025

Network failures after connection establishment

Status: Open.

#176 In w3c/network-error-logging;

· enygren opened on Jul 20, 2024

"Happy Eyeballs" failure reporting

Status: Open.

#175 In w3c/network-error-logging;

· enygren opened on Jul 20, 2024

Distribute NEL policies with DNS

privacy-trackerGroup bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Status: Open.

#173 In w3c/network-error-logging;

· simon-friedberger opened on Dec 4, 2023

WebSocket support

Status: Open.

#172 In w3c/network-error-logging;

· ricea opened on Dec 4, 2023

Only Fetch?

enhancement

Status: Open.

#170 In w3c/network-error-logging;

· LPardue opened on Oct 20, 2023

Clarify client flexibility

Status: Open.

#168 In w3c/network-error-logging;

· simon-friedberger opened on Oct 4, 2023

Rebase NEL on top of Fetch

Status: Open.

#166 In w3c/network-error-logging;

· clelland opened on Sep 29, 2023