Bug #63414 [Com]: built-in upload progress mechanism does not work with custom session handler

From: Date: Tue, 23 Aug 2016 14:36:02 +0000
Subject: Bug #63414 [Com]: built-in upload progress mechanism does not work with custom session handler
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-203516@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=63414&edit=1 ID: 63414 Comment by: mark at sasoft dot co dot za Reported by: anton dot gudkov at flatstack dot com Summary: built-in upload progress mechanism does not work with custom session handler Status: Closed Type: Bug Package: *General Issues Operating System: ubuntu 12.04 x86_64 PHP Version: 5.4.8 Block user comment: N Private report: N New Comment: Hello, Please kindly let me know why this bug was not re-opened when the user responded that they did provide feedback ? This bug is an ongoing issue and severely limits our ability to provide a decent public facing interface when uploading files when the php.ini session.save_handler is set to user (database session). Thanks Previous Comments: ------------------------------------------------------------------------ [2013-03-14 10:02:12] elena dot batmanova at flatstack dot com Hello, Please check the script Anton provided in December 2012 or kindly let us know what other feedback is required. It's very important for us to have this issue resolved. Thanks ------------------------------------------------------------------------ [2013-03-12 11:48:57] anton dot gudkov at flatstack dot com I've provided feedback on how to reproduce this issue at 2012-12-06 15:53 UTC ------------------------------------------------------------------------ [2013-02-18 00:36:05] php-bugs at lists dot php dot net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2012-12-06 15:53:21] anton dot gudkov at flatstack dot com Hi. Here is the script example which reproduces "upload progress doesn't work". Sorry for the huge script, but it couldn't be more simplier. Here is it: <?php /* if you set any writeable/readable dir to store sessions upload progress will not work. But if you comment this line, it will work. */ session_save_path('/tmp'); session_start(); $uploadName = 'test'; //upload unique name if (isset($_GET['ajax'])) { if (isset($_SESSION["upload_progress_$uploadName"])) { $progress = $_SESSION["upload_progress_$uploadName"]; $percent = round(100 * $progress['bytes_processed'] / $progress['content_length']); echo "Upload progress: $percent%<br /><pre>" . print_r($progress, 1) . '</pre>'; } else { echo 'no uploading'; } exit; } elseif (isset($_GET['frame'])) { ?> <form action="" method="POST" enctype="multipart/form-data"> <input type="hidden" name="<?=ini_get("session.upload_progress.name")?>" value="<?=$uploadName?>" /><br /> <input type="file" name="file" /><br /> <input type="submit" /> </form> <?php } else { ?> <iframe src="?frame" height="100" width="500"></iframe> <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script> <script> $(function() { setInterval(function() { $.get('?ajax', function(data) { $('#ajax').html(data); }); }, 500); }); </script> <div id="ajax"></div> <?php } ------------------------------------------------------------------------ [2012-11-21 23:21:18] chad dot scott at gmail dot com I haven't gone deep enough into the PHP source to identify what's going on, but it appears that PHP writes the upload progress session data using the handler set in "session.save_handler", ignoring any custom session handler. On Ubuntu 12.04 with the default settings, this means the data is going into "/var/lib/php5/sess_<id>". ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=63414 -- Edit this bug report at https://bugs.php.net/bug.php?id=63414&edit=1

« previous php.bugs (#203516) next »