PDF File with Dots in Filename Won't Download with PDF extension
The corporate presentation at this website downloads correctly in Microsoft IE and Chrome but not in FireFox
https://www.grantierra.com/investor-relations/presentations-events
This URL filename has multiple dots in the filename which I believe is the issues.
Is this just a FireFox bug or a configuration setting I need to change?
Isisombululo esikhethiwe
Hi dbaron99, as the-edmeister notes, you can open the PDF in Firefox's built-in viewer ("Preview in Firefox") first as a workaround.
If you right-click the direct link to the PDF and use Save Link As, Firefox doesn't add a .pdf extension to the file name. Perhaps that is because it takes the part after the last dot as the file extension (.2020-final) and feels it is not necessary. You need to add the .pdf extension yourself.
Servers can send browsers a preferred file name for saving using the Content-Disposition header, but it doesn't appear the server is doing that in this case, so each may take its best guess.
Funda le mpendulo ngokuhambisana nalesi sihloko 👍 1All Replies (2)
No problem here with Firefox downloading and displaying that PDF file for me in Firefox 76.0.1 with a Win7 PC. The PDF.JS addon in Firefox has no issue with the file name, although periods in the name are silly to use; a hyphen would make more sense, that's what I use for file saving names along that an underscore to have the file name readable while it sits on the hard drive. Been doing that since Windows came about in the early 90's.
Isisombululo Esikhethiwe
Hi dbaron99, as the-edmeister notes, you can open the PDF in Firefox's built-in viewer ("Preview in Firefox") first as a workaround.
If you right-click the direct link to the PDF and use Save Link As, Firefox doesn't add a .pdf extension to the file name. Perhaps that is because it takes the part after the last dot as the file extension (.2020-final) and feels it is not necessary. You need to add the .pdf extension yourself.
Servers can send browsers a preferred file name for saving using the Content-Disposition header, but it doesn't appear the server is doing that in this case, so each may take its best guess.