All geek questions in one place

I use the correct content type and headers. Why FireFox Saves Zip Files Without Extensions

Users on my site have the ability to upload all the photos in the album as a zip file. A zip file is dynamically created and stored in Response.OutPutStream for detection as a file download in the user's browser.

Here is the title and type of content that I output

context.Response.AddHeader("Content-Disposition", "attachment; filename=Photos.zip");
context.Response.ContentType = "application/x-zip-compressed";

.. Well, everything works fine with every browser except FireFox. Although Firefox correctly defines downloads as a Zip file, it saves the file without the .zip extension. I thought to add this heading.

context.Response.AddHeader("Content-Disposition", "attachment; filename=Photos.zip");

.. it is assumed that FF will keep the extension. I believe that I am following the correct protocol, so why does FF behave like this and how to fix it?

+3
2

:

context.Response.AddHeader("Content-Disposition", "attachment; filename=\"Photos.zip\"");
+9

, , , " " ​​ false?

0

Source: https://habr.com/ru/post/1747716/

More articles:


All Articles