Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Apache2::UploadProgress & Safari bug status??

by tlhackque (Acolyte)
on Jul 06, 2009 at 20:27 UTC ( #777667=perlquestion: print w/ replies, xml ) Need Help??
tlhackque has asked for the wisdom of the Perl Monks concerning the following question:

Apache2::UploadProgress is referenced here several times as a good solution to the large upload needs a progress meter problem. And indeed it looks good...

However, it has a documented issue: the javascript doesn't work with Safari.

OK, it's not strictly a Perl issue -- but has anyone diagnosed the problem? Better yet, fixed it?

This communication may not represent my employer's views, if any, on the matters discussed.

Comment on Apache2::UploadProgress & Safari bug status??
Re: Apache2::UploadProgress & Safari bug status??
by jhourcle (Prior) on Jul 06, 2009 at 20:44 UTC

    As the last version of Apache2::UploadProgress was released in 2006, you might want to test it, and see if it's still a problem ... or if any new ones have cropped up against other browsers.

Re: Apache2::UploadProgress & Safari bug status??
by McDarren (Abbot) on Oct 17, 2012 at 08:11 UTC
    I recently hit this same problem myself, and found that it not only doesn't work with Safari, but also Chrome.
    After much head-banging (and significant help from a co-worker), I did find a work-around.

    Edit the file /extras/progress.js, and modify line 85 as follows:

    - req.open('GET', url, Boolean(handleUploadProgressResults)); + req.open('GET', url, false);

    It appears that the call to handleUploadProgressResults will always return true in Chrome/Safari. No idea why, but modifying (hardcoding) this to false does get things working.

    cheers,
    Darren

      I don't dispute the observation, but neither the original code nor the patch makes sense. At that line, handleUploadProgressResults is NOT called; it's a reference which will be non-null, hence the Boolean will be true. It's a convoluted way of expressing 'true'. That argument to XMLHttpRequest() *should* be true - false makes the request blocking (synchronous), which is always a bad idea as it can hang the browser. If false makes the code work, something else is broken. Perhaps there is some global variable that should be in a closure. This needs more investigation...

      This communication may not represent my employer's views, if any, on the matters discussed.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://777667]
Approved by perrin
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (9)
As of 2014-08-22 13:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The best computer themed movie is:











    Results (158 votes), past polls