Re: [whatwg/fetch] Uploading a Request made from a ReadableStream body (#425)

@yutakahirano 

> we won't read response headers until we finish sending the body

How will the client handle cases of authentication problems?  That is, if the server sends a `401 Unauthorized` or some other error instead of a `100 Continue`, I would expect that this response will be accessible in JavaScript in the same way that any other response is.  Is that still the case?

> This also means we won't support redirect

Could you elaborate on this?  Suppose I'm `PUT`-ing a stream and server the server immediately sends a redirect upon receiving request headers.  (That is, no `100 Continue`, but a `307 Temporary Redirect`.)  I assume the stream in the request body would be closed, and the response from the Fetch would be available to JavaScript.  Is this the case?

-- 
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/425#issuecomment-531826527