-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Caldav limit tag on initial sync causes incorrect Caldav error response. #48678
Comments
The Enabling debug mode should also populate I haven't looked too closely, but so far the changes introduced via #47770 & #47805 align most closely with your findings. |
Hi, I reproduced and looked in the nextcloud.log. This was what came up:
It seems indeed the Caldav "UnsupportedLimitOnInitialSyncException". Probably the changes in #47770 or #47805 changed this behavior and is now producing incorrect exception behavior for Caldav. In my opinion this is clearly a bug, and it might also potentially cause issues in other Caldav errors. We are receiving more and more mails from people affected by this behavior. Is this something that can be fixed soon ? |
cc @artonge do you have a tip for us how to prevent the default exception handler to overwrite our exception? |
Hmm, maybe we should display the exception for a given set of HTTP code. Probably here: server/apps/dav/lib/Files/ErrorPagePlugin.php Lines 61 to 88 in dc92218
Update that method to display or not the exception based on the HTTP code. |
Bug description
OneCalendar users are experiencing errors when syncing caldav calendars with Nextcloud. This used to be working.
As OneCalendar developer I tried to reproduce the problem and for the latest versions of 28,29 and 30 the Caldav response is no longer working correctly when
doing a initial sync.
Hereby an overview of which versions are working correct/incorrect:
Steps to reproduce
Sync caldav calendar data:
Request data
Actual response data (507):
Expected behavior
According to https://tools.ietf.org/html/rfc6578#section-3.11 the caldav server does not need to support limit tag but in that case the following 507 response data is expected:
Nextcloud Server version
28
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
Perhaps there has been a minor update/fix of SabreDav that caused this problem in the newer 28/29/30 versions ?
The text was updated successfully, but these errors were encountered: