Broken references in Network Error Logging

[dontcallmedom-bot]

While crawling Network Error Logging, the following links to other specifications were detected as pointing to non-existing anchors, which should be fixed:

• [ ] https://fetch.spec.whatwg.org/#concept-response-trailer
• [ ] https://url.spec.whatwg.org/#concept-URL
• [ ] https://www.w3.org/TR/reporting-1/#endpoint-group
• [ ] https://www.w3.org/TR/reporting-1/#visible-to-reporting-observers

_{This issue was detected and reported semi-automatically by Strudy based on data collected in webref.}

[yoavweiss]

@clelland - can you fix the refs?

[clelland]

Most of these are easy... Trailer support, though, has been dropped from Fetch, but is still a part of HTTP, and likely part of the Chromium implementation. [[citation needed]] I may need to find a good way to rework that algorithm, since the HTTP trailers are not exposed anymore.

[clelland]

My expectations were incorrect, Chromium does not support HTTP trailers: https://source.chromium.org/chromium/chromium/src/+/main:net/http/http_chunked_decoder.h;l=78

This implementation does not bother to parse trailers since they are not used on the web.

[clelland]

(And for that matter, doesn't support the response_headers policy key, which is the only mechanism by which this processing actually occurs.