As discussed on the 2025-08-28 WebPerf WG call it appears there are differences between the error codes in the spec, Chrome, and Firefox at least.
The spec has the following:
http.response.invalidhttp.response.redirect_loop
Chrome has the following:
http.response.invalidhttp.response.invalid.empty - not in spechttp.response.invalid.content_length_mismatch - not in spec- And
http.response.redirect_loop may not be used (or is in a different code path)
Firefox:
http.response.redirect_loop- Does not use
http.response.invalid but instead returns unknown-ERROR-NUMBER (where ERROR-NUMBER is a number). Which is not spec compliant but maybe more useful (unless we add a lot more reasons to the spec so that all error codes can be mapped to one of these).
We should discuss on what is the best option here and update all three to match that. Let's discuss here, and maybe discuss at TPAC 2025?
FYI: @Bas-moz @pmeenan @rmarx @yoavweiss @nicjansma
As discussed on the 2025-08-28 WebPerf WG call it appears there are differences between the error codes in the spec, Chrome, and Firefox at least.
The spec has the following:
http.response.invalidhttp.response.redirect_loopChrome has the following:
http.response.invalidhttp.response.invalid.empty- not in spechttp.response.invalid.content_length_mismatch- not in spechttp.response.redirect_loopmay not be used (or is in a different code path)Firefox:
http.response.redirect_loophttp.response.invalidbut instead returnsunknown-ERROR-NUMBER(whereERROR-NUMBERis a number). Which is not spec compliant but maybe more useful (unless we add a lot more reasons to the spec so that all error codes can be mapped to one of these).We should discuss on what is the best option here and update all three to match that. Let's discuss here, and maybe discuss at TPAC 2025?
FYI: @Bas-moz @pmeenan @rmarx @yoavweiss @nicjansma