[whatwg/fetch] Expose Content-Length header in CORS requests (#622) from Benjamin Gruenbaum on 2017-10-29 (public-webapps-github@w3.org from October 2017)

From: Benjamin Gruenbaum <notifications@github.com>
Date: Sun, 29 Oct 2017 17:52:37 +0000 (UTC)
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/622@github.com>

As discussed with @annevk on IRC. (thanks again for the direction)

Currently Chrome and IE (but not Firefox) expose `e.total` on `ProgressEvent`s. This was discussed in https://github.com/whatwg/fetch/issues/284. 

The value of `Content-Length` is very valuable on `HEAD` requests. We sometimes make `HEAD` requests to resources in order to choose whether or not they are prohibitively expensive for the client to download or not - or to make smart decisions about downloading them.

Currently this is possible (due to `ProgressEvent`s on Chrome) but not Firefox - I think we should safelist the `Content-Length` header in CORS requests.



-- 
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/622

Received on Sunday, 29 October 2017 17:52:59 UTC