Re: [whatwg/fetch] data: URLs and Content-Length header (Issue #1834)

tharkum left a comment (whatwg/fetch#1834)

`Exposing the length would impose requirements on when that algorithm is to be run relative to everything else, no?`

The decoding of the entire URL would impose requirements on the algorithm, but I asked this question because some major browsers already do parsing (decoding) and build response in one step but do not expose "Content-Length" header to response even have all required information (decoded buffer length).

Chromium: [content/browser/data_url_loader_factory.cc](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/content/browser/data_url_loader_factory.cc)
Firefox: [netwerk/protocol/data/nsDataChannel.cpp](https://searchfox.org/mozilla-central/source/netwerk/protocol/data/nsDataChannel.cpp#49)
Servo: [components/net/protocols/data.rs](https://github.com/servo/servo/blob/main/components/net/protocols/data.rs)
WebKit: [Source/WebCore/loader/ResourceLoader.cpp](https://github.com/WebKit/WebKit/blob/ef2d6470e86c41263f13d582b55e48a5018fff26/Source/WebCore/loader/ResourceLoader.cpp#L321)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1834#issuecomment-2948422352
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1834/2948422352@github.com>