Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

In Firefox 4 how can I cause the date on downloaded files to be the current date? (Some are and some are not. In FF3 the dates were ALWAYS the current ones.)

  • 4 отговора
  • 13 имат този проблем
  • 39 изгледи
  • Последен отговор от cor-el

In Firefox 4 how can I cause the date on downloaded files to be the current date? (Some are and some are not. In FF3 the dates were ALWAYS the current ones.)

This happened

Every time Firefox opened

== I upgraded to Firefox 4 (beta)

In Firefox 4 how can I cause the date on downloaded files to be the current date? (Some are and some are not. In FF3 the dates were ALWAYS the current ones.) == This happened == Every time Firefox opened == I upgraded to Firefox 4 (beta)

Всички отговори (4)

Firefox 3.6.* and earlier set the downloaded file's modification time to the current time. In Firefox 4.0 the behavior has been changed, if a server returns a timestamp telling when the file was last modified (Last-Modified header), it is used instead.

You can revert to the previous behaviour by using the Download Timestamp add-on.

ALL other downloading software I have EVER used has ALWAYS applied the CURRENT date and time to ALL files. I sort my file managers (yes, plural) by date with newest on top. I never had to be concerned with what is a "Create" time or what is a "Modify" time.

If the developers of FF believe that the familiar and universal behavior is somehow wrong, and they want to show the server's timestamp (which is utterly useless to the end user) by default, that's fine. But then they should include a preference option to restore the familiar behavior, without requiring an add-on.

Mozilla has updated the latest Firefox 4 builds to revert back to the previous behaviour. The change back to the old behaviour will not be in beta 4, but will be in beta 5.

According to Bug 178506 (comment 194 and 218 and 220] that change has been backed out and the old behavior has been restored.