- the plupload ZIP archive (available on http://plupload.com/) comes with a sample application
- copied the contents of the ZIP file to /srv/www/htdocs/plupload/ on an openSUSE-12.1 Linux box (“HOST”) – this is where my Apache2 httpd serves HOST/plupload/ resp. HOST/plupload/examples/custom.html from
- where does the application want to get the files uploaded to? silly me didn’t have a close enough look at that for too long
- plupload/examples/upload.php has a $targetDir for that; apparently the proper way would be to set upload_tmp_dir in the system php.ini (which is de-commented there, so that we don’t get files dropped, where we don’t expect them, and for as long as we don’t expect them); but for our local experiments we choose the other branch and set it to our local plupload/examples/uploads/ directory (i.e. /srv/www/htdocs/plupload/uploads/) – success: it works!!!
- we have a working application
- the Apache log-files don’t actually mention the file uploaded – that’s sad, but why should I care?
which browsers and front-ends resp. front-end plugins talking to the Apache httpd work?
- Mac OS X: Chromium 22.0.1204.0 / Firefox/16.0 / Safari (6.0 (7536.25)) together with “html5” / “flash” / “silverlight“
- openSUSE-12.1/12.2 : Chromium 22.0.1126.0 / Firefox/15.0 together with “html5” / “flash“
- Android 4.0.3 (on a Samsung Galaxy SII): the built-in browser (AppleWebKit/534.30) / Chrome 18.0.1025.166 (AppleWebKit/535.19) together with “html5“
- Android 3.1 (on a Samsung Galaxy Tab 10.1): the built-in browser browser (AppleWebKit/534.13) together with “html5” / “flash“
- WinXP (5.1.2600 Service Pack 3 Build 2600): IE8 together with “html4” / “flash” / “silverlight” (“html5” does not exist) / Chrome 22.0.1229.39 with “html5” / “html4” / “flash“
- [now] …
- [To Be Done] what about trying a couple of browsers on other Windows platforms?
- …