- From: Dominic Farolino <notifications@github.com>
- Date: Wed, 15 Mar 2023 18:40:35 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/1614/review/1342732281@github.com>
@domfarolino commented on this pull request. > - <p>If the <a for=/>request</a>'s <a for=request>mode</a> is "<code>navigate</code>" and its - <a for=request>redirect mode</a> is "<code>manual</code>", then callers need to follow a very - specific flow with this algorithm to get the intended behavior. They should compute the - appropriate <a for=response>location URL</a>, and if it is non-null or failure, then they should - call <a for="fetch controller">process the next manual redirect</a>. This will result in - <a for=fetch><i>processResponse</i></a> being called again, with the next <a for=/>response</a> - in the redirect chain. - - <dt><a for=fetch><i>processResponseEndOfBody</i></a> - <dd><p>Takes an algorithm that will be passed a <a for=/>response</a>. Indicates the network is - done transmitting the response. This does not read <a for=/>response</a>'s - <a for=response>body</a>. + <p>This is the most common way in which clients handle a <a for=/>response</a>, for example + <a lt="fetch a classic script">scripts</a> and <a lt="fetch a style resource">style resources</a>. + The <a for=/>response</a>'s <a for=response>body</a> is downloaded in its entirety into a + <a>byte sequence</a>, and then processed by the <a for=request>client</a>. Or... maybe the PR preview is out of date with the spec text? I'm not sure what's happening... -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1614#discussion_r1137989404 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1614/review/1342732281@github.com>
Received on Thursday, 16 March 2023 01:40:48 UTC