Re: [whatwg/fetch] Use request's current url as base URL in redirects (#633)

So I think with this change we end up doing what I think is the correct thing for opaque redirects, but it doesn't quite work for synthetic redirects not created through `Response.redirect()` (those are protected because the URL is already parsed and headers are immutable):
```js
const res = new Response(null, { status: 302 });
res.headers.append("Location", "something-relative");
```
In order to make this work we'd have to parse the `Location` header if status is a redirect status when it's first stored/used somewhere. Otherwise those responses would always end up being relative to the current request.

But maybe we should live with that inconsistency? Not entirely sure how to fix it.

-- 
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/633#issuecomment-381420434