nextcloud
[Bug]: Uploading PDF with the same name as previously deleted PDF - content of deleted PDF reappears
⚠️ This issue respects the following points: ⚠️
- [x] This is a bug, not a question or a configuration/webserver/proxy issue.
- [x] This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- [x] Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- [x] I agree to follow Nextcloud's Code of Conduct.
Bug description
NextCloud 31.0.2, fresh install, no upgrade history PDF viewer system app version 4.0.0 Encryption enabled
Upload PDF with some content:
Single click to open preview:
Checksum app:
Delete file (+ clear trash bin to be sure)
Upload PDF with DIFFERENT content, but under the name as previously deleted PDF and in the SAME folder
Single click to open preview: this is the content of the previous (deleted) file! the actual uploaded file has different content.
Checksum app -- different checksum than old file
On the screenshot below is the content of that newly uploaded PDF (screenshot captured from local Adobe prior to uploading to NextCloud)
Apparently this bug is specific to PDF. Office and text files are not affected by this error.
This bug does not appear if you upload PDF under different file name AND/OR upload new PDF to a different folder.
Steps to reproduce
Above
Expected behavior
Deleted PDF should not be available anymore.
Nextcloud Server version
31
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
Nginx
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- [ ] Default user-backend (database)
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Unable to reproduce.
Please:
- test in a supported release (31.0.2 is multiple patch levels out-of-date)
- confirm your Nginx configuration is up-to-date with that described in the v31 manual (https://docs.nextcloud.com) particularly since both asset caching and header configuration are relevant here
- check your browser console Network tab to see what the PDF PROPFIND and GET transactions look like
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
