- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Sun, 05 Jun 2011 09:06:05 -0700
On 6/3/11 2:58 PM, Bjartur Thorlacius wrote: > On 6/3/11, Boris Zbarsky<bzbarsky at mit.edu> wrote: >> On 6/3/11 11:46 AM, Bjartur Thorlacius wrote: >>>> Note that some browsers will do weird parsing of the query params to >>>> attempt to extract a "useful filename". That seems strictly worse than >>>> just using Content-Disposition. >>>> >>> That's slightly better than just using the last non-empty path >>> component, though. >> >> It's not, because they're not consistent about it... >> > Why need they be? This isn't Bittorrent. Use the last non-empty path > component for a short name prone to accidental clashes, or the title > for a verbose, unportable and descriptive name. It's purely a hint for > user convenience (so they don't have to invent their own names or > retype the title). What a file is named on a client's machine is > purely the client's matter. I think you completely misunderstood my mail... the point is that browses do NOT all use the last non-empty path component; some try to guess a filename based on the query params, in various ways. -Boris
Received on Sunday, 5 June 2011 09:06:05 UTC