Bug#750736: iceweasel: PDF preview / user's mailcap file are not taken into account for some PDF files

[Vincent Lefevre]

On 2014-06-06 21:38:09 +0900, Mike Hommey wrote:
> Since you're not giving an url, i'll venture a guess:

I didn't give a URL because it is private. So, I gave all information
Iceweasel was presenting to me. Iceweasel should really make the
associated HTTP headers avaiable for bug reports. I could get them
with the Live HTTP headers extension (but that's a bit impractical
because one gets information for all the tabs...):

HTTP/1.1 200 OK
Date: Fri, 06 Jun 2014 14:58:25 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-AspNetMvc-Version: 4.0
Content-Disposition: attachment; filename*=UTF-8''Pr%C3%A9cision%20T7610.pdf
Cache-Control: private
Content-Type: application/.pdf
Content-Length: 418127

> https://github.com/mozilla/pdf.js/issues/3121

FYI, that's worse with the extension: I can't even view the PDF file,
the only option is to save it.

> The .mailcap issue is unrelated and is just the good old mailcap issue
> that iirc you yourself reported a long while ago.

I don't remember. There was one about unknown content type:

  https://bugzilla.mozilla.org/show_bug.cgi?id=638300

but that's not the case here since it is recognized as PDF: the
vprerex PDF viewer is proposed, but that's from /etc/mailcap[*],
while my ~/.mailcap should have the precedence. This is the first
time I can see such a behavior (vprerex was installed a few days
ago, due to a TeX Live upgrade).

[*] application/pdf; vprerex %s; test=test -n "$DISPLAY"

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)