Open tato-rj opened 1 year ago
I just switched these from true to false and it now works. Session is now false
and Browser is now true
. Can anybody explain why? Can I keep it this way?
'use' => [
'session' => false, // should the chunk name use the session id? The uploader must send cookie!,
'browser' => true, // instead of session we can use the ip and browser?
],
In case of session
the session id is used as part of the identifier.
When browser
is used, then the md5 hash of the user IP and user agent is used.
The session ID is probably changes every time because the browser blocks the set cookie or just simply does not sends it because the request is cross-domain.
It is better to use the session identifier because the IP and the user agent might be empty and can be the same between users.
Got it, thanks for the reply. Is there a specific cookie I should be sending from the sender app to the receiver?
@tato-rj same issue but setting browser true and session false in config not working for me
What steps will reproduce the problem?
I am using resumable.js to upload the file. The resumable.js is in one website, and the backend chunk-upload is in another (it all works well if both are on the same site).
What is the expected result?
When both frontend and backend are in the same site, it all works. The chunks are created and the
$fileReceived->isFinished()
is triggered as expected.What do you get instead?
When the file is sent from a different site (which is the setup I need), the chunks are created but the
$fileReceived->isFinished()
never gets called.Additional info
When logging the
$fileReceived->handler()->getPercentageDone()
, I noticed something interesting: This is the log when all works well (both frontend and backend are in the same site)And here is the log when it doesn't (frontend and backend are in different sites)