Under certain conditions, the CSRF token from the 'X-Csrftoken' HTTP header is incorrect, leading to the frontend presenting an error message to the uploadee. Still unclear how to re-produce the exact conditions, but it seems to mostly be triggered by the latest Chrome verions.
The upload mechanism was re-worked in Devilry 5.4 (#1219). My guess is that the issue has something to do with the cookie handling for the file uploader.
Under certain conditions, the CSRF token from the 'X-Csrftoken' HTTP header is incorrect, leading to the frontend presenting an error message to the uploadee. Still unclear how to re-produce the exact conditions, but it seems to mostly be triggered by the latest Chrome verions.
The upload mechanism was re-worked in Devilry 5.4 (#1219). My guess is that the issue has something to do with the cookie handling for the file uploader.