Date: Sat, 31 Dec 2005 11:55:03 +0300 From: Andrey Chernov <ache@FreeBSD.ORG> To: Martin Cracauer <cracauer@cons.org> Cc: freebsd-current@FreeBSD.ORG, Colin Percival <cperciva@FreeBSD.ORG> Subject: Re: fetch extension - use local filename from content-dispositionheader (new diff) Message-ID: <20051231085503.GA73324@nagual.pp.ru> In-Reply-To: <20051230142848.A36879@cons.org> References: <20051229221459.A17102@cons.org> <030d01c60cf1$db80a290$1200a8c0@gsicomp.on.ca> <20051230035724.GA52167@nagual.pp.ru> <20051230125227.A33408@cons.org> <43B580D2.9070609@freebsd.org> <20051230142848.A36879@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 30, 2005 at 02:28:48PM -0500, Martin Cracauer wrote: > The content-disposition header is a standard web feature that we have > no good reason to ignore (as long as we don't turn it on unless > directly user-requested). We are just advancing with web technology, > which partly moves from explicit naming in URLs to simpler (for them) > schemes. There is easy way to make most security hackarounds unneeded in the way like every browser does: confirm final file name interactively. I.e. fetch can do something like this: Save as filename.exe (Y/N)? -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051231085503.GA73324>