From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 08:55:07 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77A0016A420; Sat, 31 Dec 2005 08:55:07 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2770343D60; Sat, 31 Dec 2005 08:55:05 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.4/8.13.4) with ESMTP id jBV8t43O073472; Sat, 31 Dec 2005 11:55:04 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.4/8.13.4/Submit) id jBV8t3Bf073471; Sat, 31 Dec 2005 11:55:03 +0300 (MSK) (envelope-from ache) Date: Sat, 31 Dec 2005 11:55:03 +0300 From: Andrey Chernov To: Martin Cracauer Message-ID: <20051231085503.GA73324@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Martin Cracauer , Colin Percival , freebsd-current@FreeBSD.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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051230142848.A36879@cons.org> User-Agent: Mutt/1.5.11 Cc: freebsd-current@FreeBSD.ORG, Colin Percival Subject: Re: fetch extension - use local filename from content-dispositionheader (new diff) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 08:55:07 -0000 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/