Upload progress indicator (and some other progress bars) is running forever in Firefox

dup of http://drupal.org/node/49501

I suspect that this is caused by your browser caching an older version of the JavaScript files. Try clearing the browser's cache and then using the file uploads.

Just trying to add some claification on this bug which may help to find a solution.
The progress bar hangs only on Linux browsers.
Browsers on Windows and Mac don't seem to have a problem.
The server OS running drupal 4.7 beta 5 seems to make no difference.

Can't we fix this with something like the following code?

header("Expires: Mon, 26 Jul 1997 05:00:00 GMT");                 // Date in the past
header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT");  // Altijd veranderd
header("Cache-Control: no-store, no-cache, must-revalidate");  // HTTP/1.1
header("Cache-Control: post-check=0, pre-check=0", false);
header("Pragma: no-cache");                                              // HTTP/1.0

Just a guess...

Using the folowing AJAX request, it is possible to refresh some cached file:

var xmlHttp = new XMLHttpRequest();
xmlHttp.open("GET","path/to/file/that/has/to/be/refreshed",false);
xmlHttp.setRequestHeader("If-None-Match","some-random-string");
xmlHttp.setRequestHeader("Cache-Control","no-cache,max-age=0");
xmlHttp.setRequestHeader("Pragma","no-cache");
xmlHttp.send();

But still we don't have a way to check whether we have an old version of the file or the new one.

My suggestion would be to have version information in javascript/css/image filenames, just like here:
drupal-4.7.0.js
update-4.7.0.js
progress-4.7.0.js
drupal-4.7.0.css

So after every Drupal upgrade, all the users' browsers would be forced to get the newest versions of the files.

-----
Archatas
http://hyperlocal.org

Stefan, if we use headers like in your example, at first, we will need php file wrappers for all javascript/css/image files. Secondly, the files will never be cached, as they normaly should.

I am inclined to mark this won'tfix.

1: its a browser issue. File an issue with firefox :)
2: not many people will upgrade twice. If you really do so, make sure you wipe your cache, or use a browser w/o the issue (konqueror)
3: We need a lot of code to fix this minor issue. Only AJAX will not help. Giving files version numbers is horrible. And adding PHP wrappers around all files is a severe performance issue.

Should I mark it as such?

it is trivially fixed by adding a timestamp to the js file. we should do that at leats in the update page because failures rthere are scary and sometimes fatal for a sysadmin without skills.

It is not only Firefox.
The problem occurs in Opera 7.54, Epiphany 1.6.5, Konqueror and other browsers on linux when trying to attach a file to a page.
That also rules out a browser cacheing issue.

@moshe, excuse me if this is a stupid, but can you point me to a resource, or give a hint how to fix this? I would like to help make the upgrade a bit more sturdy. Every small fix or improvement is welcome AFAIKS.

Bèr

in HTML

<script src=misc/drupal.js?date=123456789>

since the date always changes, the stylesheet is never cached. recommended for update.php not everywhere.

try latest HEAD. we fixed some stuff. please reopen with details if still not fixed.