- From: Mike West <notifications@github.com>
- Date: Wed, 28 Aug 2019 05:25:02 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/925/review/280789107@github.com>
mikewest commented on this pull request. > @@ -564,6 +572,22 @@ A: 3 <var>name</var> and <a for=header>value</a> is <var>value</var> to <var>list</var>. </ol> +<p>To <dfn export for="header list" id=concept-header-list-set-structured-header>set a structured +header</dfn> <a for=header>name</a>/<a>structured header</a> +<var>name</var>/<var>structured header</var> pair in a <a for=/>header list</a> <var>list</var>, run +these steps: + +<ol> + <li>Let <var>serialized value</var> be the result of executing the <a>serializing structured + headers</a> algorithm on <var>structured header</var>. + <li><a for="header list">Set</a> <var>name</var>/<var>serialized value</var> in <var>list</var>. +</ol> + +<p class="note">Structured header values are defined as objects which HTTP can (eventually) +serialize in interesting and efficient ways. [[!HEADER-STRUCTURE]] For the moment, Fetch only +supports setting these objects in <a for=/>header lists</a> by first serializing them into a +string representation. I added another line about future efficiency gains. Any additional suggestions for the encouragement you'd like to provide here? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/925#discussion_r318549483
Received on Wednesday, 28 August 2019 12:25:24 UTC