Update header value check of XHR/Fetch API to RFC 7230 (No longer pursuing)

We are planning to normalize and check strictly against RFC 7230 the header values, in XHR's setRequestHeader() and Fetch API's JavaScript interfaces. Values containing the following octets are rejected: 0x01 -- 0x08, 0x0B, 0x0C, 0x0E - 0x1F, and 0x7F. Leading/trailing HTTP whitespace bytes (i.e. the following octets) are removed: 0x09, 0x0A, 0x0D, and 0x20. Spec: https://fetch.spec.whatwg.org/#concept-header-value https://fetch.spec.whatwg.org/#concept-header-value-normalize


Editor's draft

Status in Chromium


No longer pursuing (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signal
  • No signals


Last updated on 2019-10-31