Re: [whatwg/fetch] Location header is the empty string (#669)

To me the steps appear unclear:

> 5.2. Let location be the result of extracting header list values given `Location` and actualResponse’s header list.
>
> 5.3. If location is a value, then set location to the result of parsing location with actualResponse’s url.

I'm not sure when location could ever be a value; "extract header list values" returns either null or a list. Seems like a spec bug.

But if we assume that conditions is not triggered, then we set location URL to null. Then in HTTP-redirect fetch step 2, response gets returned, so more like Chrome's behavior.

So per the spec as written I think Chrome's behavior makes sense. But the spec has a pretty bad bug in this area which casts doubt on the result, IMO.

I'm curious to see what your analysis was; perhaps I missed something.

-- 
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/issues/669#issuecomment-364445809