Editorial: align with Fetch's structured field changes #5732
Conversation
|
It seems this is the only IETF document for which we reference httpwg.org and we only do so in HTML. It doesn't matter much, but any issue if I changed it to tools.ietf.org? |
|
I'd slightly prefer to update all the other "structured header" references, e.g. in prose, at the same time. (And ideally even the I'd prefer to go the other way around and use httpwg.org more, as it's infinitely more readable. |
|
So "structured header" is still a valid term. It's just that in Fetch I want to be prepared for trailers. I'm not sure HTML needs to be. I could go either way though. |
|
I think it'd be good to be consistent; otherwise the reader is left wondering. And e.g. |
|
It's not, it says so right in the Abstract and onward? |
|
Can we land this then? As for httpwg.org, I'd prefer an official IETF reference for longevity. It would be nice if IETF could format all their documents that way though. |
|
I'd still prefer that we be consistent, and at least change the document title and citation name. |
|
The document title is already correct, no? And changing the citation name would break links or there a way to avoid doing that? |
|
You're right about the document title. What links are you worried about breaking? |
|
Into the references section? |
|
If we just do |
| @@ -80498,12 +80497,11 @@ interface <dfn>BarProp</dfn> { | |||
| <ol> | |||
| <li><p>Let <var>policy</var> be a new <span>embedder policy</span>.</p></li> | |||
|
|
|||
| <li><p>Let <var>parsedItem</var> be the result of <span | |||
| data-x="concept-response-header-list-get-structured-header">getting a structured header</span> | |||
| <li><p>Let <var>parsedItem</var> be the result of <span>getting a structured field value</span> | |||
| with `<code>Cross-Origin-Embedder-Policy</code>` and "<code data-x="">item</code>".</p></li> | |||
There was a problem hiding this comment.
If you'd like to fix this while you're here, it should be suffixed with "from response's [header list]"
| @@ -80517,13 +80515,12 @@ interface <dfn>BarProp</dfn> { | |||
| </ol> | |||
| </li> | |||
|
|
|||
| <li><p>Set <var>parsedItem</var> to the result of <span | |||
| data-x="concept-response-header-list-get-structured-header">getting a structured header</span> | |||
| <li><p>Set <var>parsedItem</var> to the result of <span>getting a structured field value</span> | |||
| with `<code>Cross-Origin-Embedder-Policy-Report-Only</code>` and "<code | |||
| data-x="">item</code>".</p></li> | |||
See whatwg/fetch#1056.
/infrastructure.html ( diff )
/origin.html ( diff )
/references.html ( diff )