TypeError when redirect is set to 'manual'

[KhafraDev]

Bug Description

A TypeError is thrown when using { redirect: 'manual' } (this did work in older versions)

Reproducible By

import { fetch } from 'undici';

const r = await fetch('https://httpbingo.org/redirect-to?url=http%3A%2F%2Fexample.com%2F', {
    redirect: 'manual'
});

console.log(r.headers.get('location'));

Expected Behavior

No TypeError

Logs & Screenshots

\node_modules\undici\lib\fetch\index.js:176
        Object.assign(new TypeError('fetch failed'), { cause: response.error })
                      ^

TypeError: fetch failed
    at Object.processResponse (\node_modules\undici\lib\fetch\index.js:176:23)
    at fetchFinale (\node_modules\undici\lib\fetch\index.js:720:17)
    at EventEmitter.mainFetch (\node_modules\undici\lib\fetch\index.js:695:5)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  cause: undefined
}

Environment

Windows 10, node v16.11.0, undici v4.8.1

Additional context

without much debugging the status is set as 0 so I suspect it's never updated from its default value for some reason

[ronag]

What is the behavior in chrome?

[KhafraDev]

What is the behavior in chrome?

afaict Chrome/FF both handle this correctly but there are no headers (however this did work previously in undici which confused me lol)

also the Response seems to be set to default values (and statusCode = 0 which causes the TypeError):

[KhafraDev]

So I dug into it a little deeper and the reasoning:

"manual"
    Retrieves an opaque-redirect filtered response when a request is met with a redirect, to allow a service worker to replay the redirect offline. 
    The response is otherwise indistinguishable from a network error, to not violate atomic HTTP redirect handling. 

Essentially the response is the same as a network error, but isn't classified as one. That's the reason the status is 0, headers are empty, etc. However undici shouldn't throw a TypeError when a Response's status is 0 and redirect is set to 'manual'.