From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [69.252.207.44]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 8A0947AACE for ; Fri, 10 Apr 2015 04:50:33 -0700 (PDT) Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-12v.sys.comcast.net with comcast id EBoN1q0012VvR6D01Boel3; Fri, 10 Apr 2015 11:48:38 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-19v.sys.comcast.net with comcast id EBod1q00B5LMg2101Bod4H; Fri, 10 Apr 2015 11:48:38 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.3+ Date: Fri, 10 Apr 2015 07:48:37 -0400 Message-ID: <20150310074837.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1428666518; bh=S8SBybSHxgUITbVE8DXkG7UvZynvSR1HOJ7BgB2ui+o=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=FLKc8yBROE4kiPl1QQdg5VVYTiUbDl052rmiQ2+ZHIgPUAZRTQuWt9mD2UKltjTRi IZ1eTHvKIPqV37JUvxWSxFT3eG1WNyaP6GH49ZO7CzXiNoGrr+aHDr+S79GYtcztlM pK6O2NaHl8aY1VIVa+sSh5AqulooFqF7DlA0HYH+bl6101+DJHfhKcInOe9LKHfW67 +mnMq3rTQJ8s4PSXHvz6t2KVYRaZBYuqJgy6Xqs9FVSlqht+jTKljZV+hGb+2BQpfz ZaxuLe6/KRD5lvFyFrs8er3EBnZq7OmXvkvhjDBNHxHCpy69l9MgvgtErCgvkVRpPt 83mWtqBip63mQ== Subject: [Edbrowse-dev] pdf auto download X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2015 11:50:33 -0000 > I'd just alter the existing mime mechanism to support a contenttype keyword Ok I see where you're headed here. That makes sense. Then, along with the program to run to process that type of file, would be some kind of download attribute if you want the option to download that file to disk. But I wonder if it shouldn't be the other way round: default for anything other than text is to give you the option to download, and if you want things always rendered, always want to read the pdf or hear the music, then some kind of render or inmemory keyword. There are zillions of types of files out there and almost all of them, other than text, I would want the download option, which is why I'm thinking that would be the default. In my config, my personal preference, a mime type application/pdf, that would bypass autodownload and run my particular pdf converter, which really should not be hardcoded as it is today in http.c. I'd still support suffixes for local browsing, strolling through a directory, load a file, and type pb (play buffer) for example and it knows which player to invoke by suffix, but as you say this would mostly be for local files, whereas web should use content type most of the time. Karl Dahlke