Upload progress events and redirects

I request a URL using POST that redirects using 307 to some other URL.
This will result in the request entity body being transmitted twice.
It seems however user agents only fire progress events as if only one
fetch happened. Is that how we want to define this?

I guess arguably that's how we define fetching in general (ignoring
redirects) but it does mean you have to wait for the response (to see
if it's a redirect or 401/407) before you can dispatch loadend on
.upload which is contrary to what we decided a little over a year ago:

What do people think?


Received on Tuesday, 16 April 2013 15:59:35 UTC