Filter types on Network Error Login (NEL) reports

Rfraile

4/4/24, 9:50 AM

I have implemented (NEL) Network Error Login with this headers:

nel: {"report_to":"default","max_age":3600,"failure_fraction":0.5}
report-to: {"group":"default","max_age":3600,"endpoints": 
[{"url":"https://example.com/input"}]}

But getting all type of errors are overloading the quota for the service. As the documentation points there are the following ones by default:

dns.unreachable
dns.name_not_resolved
dns.failed
dns.address_changed

tcp.timed_out
tcp.closed
tcp.reset
tcp.refused
tcp.aborted
tcp.address_invalid
tcp.address_unreachable
tcp.failed
tls.version_or_cipher_mismatch
tls.bad_client_auth_cert
tls.cert.name_invalid
tls.cert.date_invalid
tls.cert.authority_invalid
tls.cert.invalid
tls.cert.revoked
tls.cert.pinned_key_not_in_cert_chain
tls.protocol.error
tls.failed

http.error
http.protocol.error
http.response.invalid
http.response.redirect_loop
http.failed
abandoned

As the http.* ones have a large number of reports and we've covered them with other tools, is it possible to avoid browsers to send them?

0 + 0

networking

monitoring

network-monitoring

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Filter types on Network Error Login (NEL) reports

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.