- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 19 Sep 2013 20:24:26 -0700
- To: Julian Aubourg <j@ubourg.net>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, Anne van Kesteren <annevk@annevk.nl>, WebApps WG <public-webapps@w3.org>
On Thu, Sep 19, 2013 at 8:10 PM, Julian Aubourg <j@ubourg.net> wrote: > Sure, what I actually meant is that you'd need to somehow pre-parse the data > URL to extract the exact length before storage. Dunno how > desirable/desired/common this is. I would hardly call taking the length subtracting any characters before the "," and applying a multiplier "parsing". You don't have to look at any characters after the "," at all. / Jonas > On 20 September 2013 04:58, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> >> On 9/19/13 10:51 PM, Julian Aubourg wrote: >>> >>> But Content-Length is not the same as the length of the string >>> containing the Data URL. >> >> >> Sure. It can also be a simple formula computed from that length, in the >> case of base64-encoded data URLs. >> >> And of course you have to subtract out the length of the parts before ','. >> None of this is all that hard to do. >> >> -Boris > >
Received on Friday, 20 September 2013 03:25:27 UTC