Edit report at https://bugs.php.net/bug.php?id=74131&edit=1
ID: 74131
Updated by: laruence@php.net
Reported by: fred5 at originsystems dot co dot za
Summary: session.upload_progress doesn't work for database
sessions
Status: Open
Type: Bug
Package: Session related
Operating System: CentOS 7
PHP Version: 7.0.16
-Assigned To:
+Assigned To: krakjoe
Block user comment: N
Private report: N
New Comment:
I am not sure what apcu's plan, I am assigning this to the author
Previous Comments:
------------------------------------------------------------------------
[2017-02-20 21:33:39] fred5 at originsystems dot co dot za
Hi Laurence,
It appears that the hack I've suggested below won't work as it causes a "chicken and
egg" situation ie. $_SESSION is not populated until session_start() but
session_set_save_handler() must be executed prior to session_start()
The above means a recode of our "progress check" ajax call as a complete anomaly for our
development framework (as it would be the only component in the entire application not using our
standard session handling mechanism).
The above is something we'd really like to avoid if possible so it becomes even more desirable
for us to be able to utilise APCu and apc.rfc1867 as we have been doing.
I would thus really appreciate any feedback you can provide regarding whether the fact that
apc.rfc1867 not working is something I can / should log a bug for in order to get resolved.
I look forward to hearing from you - thanks!
------------------------------------------------------------------------
[2017-02-20 12:56:55] fred5 at originsystems dot co dot za
thanks again!
Regarding:
1. I am not sure why you think php doesn't support rfc1867
In PHP 7, even with both APCu and APC Backward Compatibility (apc-bc) installed, the apc.rfc1867
keys no longer show in phpinfo, and are likewise not accessible when uploading using apc. So the
upload does not work.
Please see here for explanation of the problem: https://github.com/krakjoe/apcu-bc/issues/22
My 100% first prize at this point would be able to continue to use APC. With this in mind should I
open a separate bug for getting the apc.rfc1867 keys re-instated? (they are still very much included
in the PHP documentation)
2. Your suggestion regarding session.upload_progress
We have a standard handling that applies to every call made to the server. In every case, Session is
set up as the first step, which means that we would need to take something like the following
approach:
Within Session::__construct() {
...
$fileSESSION = $_SESSION;
session_set_save_handler($this,true);
array_merge($_SESSION,$fileSESSION); // ensuring that fileSESSION takes value priority
...
It does however seem a bit of a hack and has the following drawbacks that I can think of:
- Redundant session files get created that will need to be managed; and
- The above is redundant overhead in every call except for those during file upload
- On completion of file upload, redundant $_SESSION file upload information will be retained
The above reasons as well as the fact that we have significant investment already in APC is why I
would vastly prefer to continue using APC apc.rfc1867 if at all possible.
Please do let me know what you think - thanks again.
------------------------------------------------------------------------
[2017-02-20 12:23:23] laruence@php.net
apcu use an internal cache to cache upload progress, php7 use session(according to
session.save_handler) to cache that info;
I am not sure why you think php doesn't support rfc1867, the problem here is, when php is
receiving upload progresss infos from webserver, no user codes has been executed, when php is try to
store upload porgress infos into session, how do he knows that you are using database session save
handler?
you can still get upload progress infos before you calling set_save_handler(which change the
session.save_handler that php used to cache progress info .)
------------------------------------------------------------------------
[2017-02-20 11:56:18] fred5 at originsystems dot co dot za
Thanks very much for the candid feedback Laurence.
We are on PHP 5.6 and currently use APCu cache with apc.rfc1867 very successfully. We have provided
reliable progress bar information to our customers for some years now using this technique.
The problem for me really is as follows:
1. Your answer renders session.upload_progress useless to us (and anyone using database sessions)
See: http://stackoverflow.com/q/29867392/3051627
2. PHP 7 seems to have dropped support for apc.rfc1867 in the APCu cache.
See: http://stackoverflow.com/q/42309168/3051627
3. We support client browsers as far back as IE9, so are unable to use the new HTML5 browser
capabilities
See: https://developer.mozilla.org/en-US/docs/Using_files_from_web_applications
The combination of these things effectively means that we are unable to upgrade to PHP 7 - which is
critical for us!
I'll be honest; at the moment I'm feeling like PHP has abandoned us entirely by dropping
support for critical features without providing a workable replacement, but I am hoping that this is
a lack of knowledge on my part and that there is some tricky way of achieving a file progress bar in
PHP 7 that can both:
1. support older browsers; and
2. work with database sessions
Is there possibly any advice you can give me that will allow us to achieve the above in PHP 7? (for
example is it possible that the apc.rfc1867 values could be made available again in APCu)
thanks again for your very prompt feedback.
------------------------------------------------------------------------
[2017-02-20 11:22:33] laruence@php.net
in that case, I understand what the problem is now. I am afraid that is no way to "fix",
because php receiving upload is ahead of any user codes being executed.
------------------------------------------------------------------------
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=74131
--
Edit this bug report at https://bugs.php.net/bug.php?id=74131&edit=1