[Bug]: NC replies with HTTP status code 500 instead of 4xx when uploading invalid CalDAV entries. #46380

nagmat84 · 2024-07-09T16:52:00Z

⚠️ This issue respects the following points: ⚠️

This is a bug, not a question or a configuration/webserver/proxy issue.
This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
I agree to follow Nextcloud's Code of Conduct.

Bug description

Nextcloud replies with HTTP status code 500 and message This recurrence rule does not generate any valid instances for the following inconsistent CalDAV entry

BEGIN:VCALENDAR
  VERSION:2.0
  PRODID:DAVx5/4.4.0.1-gplay ical4j/3.2.18 (com.google.android.calendar)
  BEGIN:VEVENT
    DTSTAMP:20240615T063700Z
    UID:9ae55fad-b059-451c-94bd-f48f6b47d14c
    SEQUENCE:2
    SUMMARY:Technik
    DTSTART;TZID=Europe/Berlin:20240707T110000
    DTEND;TZID=Europe/Berlin:20240707T121500
    RRULE:FREQ=WEEKLY;WKST=TU;UNTIL=20240713T215959Z
    EXDATE;TZID=Europe/Berlin:20240728T110000
    EXDATE;TZID=Europe/Berlin:20240707T110000
  END:VEVENT
END:VCALENDAR

Obviously, NC is right to reject the calendar entry and the error message is correct. However, the HTTP status code should be 4xx, not 500. HTTP status codes 5xx indicate a server-side error, but this error is a client-side error. A 5xx status code informs the client to try to repeat the same request later, but in this case the same request will fail again.

More suitable status codes are 409 (Conflict) or 422 (Unprocessable Content). The latter is probably the most suitable status code.

I am using an Android smartphone with Google Calendar as the front-end UI and DAVx5 as the connector. I was somehow able to create the event above and DAVx5 become stuck, because it had the event in its local cash and endlessly tried to send the event to the NC server.

I am aware that there is a bug on several layers here. The Google Calender UI should prevent a user from creating such inconsistent events in the first place. But NC should also respond with the correct status code.

Steps to reproduce

Create an invalid VEVENT entry with recurrences but zero instances
Try to upload that VEVENT to NC server
NC responds with HTTP status code 500

Expected behavior

NC should respond with a 4xx status code, preferably 409 or 422

Installation method

Community Manual installation with Archive

Nextcloud Server version

29

Operating system

Other

PHP engine version

PHP 8.2

Web server

Apache (supported)

Database engine version

PostgreSQL

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?

Default user-backend (database)
LDAP/ Active Directory
SSO - SAML
Other

Configuration report

{
    "system": {
        "dbtype": "pgsql",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "default_language": "de",
        "default_locale": "de_DE",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpmode": "sendmail",
        "overwrite.cli.url": "https:\/\/cloud.mhnnet.de\/",
        "htaccess.RewriteBase": "\/",
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "localhost",
            "mhnnet.de",
            "www.mhnnet.de",
            "server.mhnnet.de",
            "cloud.mhnnet.de",
            "famna.de",
            "www.famna.de",
            "cloud.famna.de"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "version": "29.0.3.4",
        "dbtableprefix": "oc_",
        "dbport": "",
        "installed": true,
        "maintenance": false,
        "theme": "",
        "loglevel": 2,
        "default_phone_region": "DE",
        "memcache.local": "\\OC\\Memcache\\APCu",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 0,
            "timeout": 0
        },
        "enabledPreviewProviders": [
            "OC\\Preview\\BMP",
            "OC\\Preview\\GIF",
            "OC\\Preview\\HEIC",
            "OC\\Preview\\JPEG",
            "OC\\Preview\\Krita",
            "OC\\Preview\\MarkDown",
            "OC\\Preview\\MSOffice2003",
            "OC\\Preview\\MSOffice2007",
            "OC\\Preview\\MSOfficeDoc",
            "OC\\Preview\\Movie",
            "OC\\Preview\\MP3",
            "OC\\Preview\\OpenDocument",
            "OC\\Preview\\PDF",
            "OC\\Preview\\PNG",
            "OC\\Preview\\SVG",
            "OC\\Preview\\TIFF",
            "OC\\Preview\\TXT",
            "OC\\Preview\\WebP",
            "OC\\Preview\\XBitmap"
        ],
        "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory",
        "maintenance_window_start": 1
    }
}

List of activated Apps

Enabled:
  - activity: 2.21.1
  - bruteforcesettings: 2.9.0
  - calendar: 4.7.10
  - cloud_federation_api: 1.12.0
  - contacts: 6.0.0
  - dashboard: 7.9.0
  - dav: 1.30.1
  - federatedfilesharing: 1.19.0
  - federation: 1.19.0
  - files: 2.1.0
  - files_accesscontrol: 1.19.1
  - files_downloadlimit: 2.0.0
  - files_sharing: 1.21.0
  - files_trashbin: 1.19.0
  - files_versions: 1.22.0
  - groupfolders: 17.0.1
  - logreader: 2.14.0
  - lookup_server_connector: 1.17.0
  - mail: 3.7.2
  - nextcloud_announcements: 1.18.0
  - notifications: 2.17.0
  - oauth2: 1.17.0
  - password_policy: 1.19.0
  - previewgenerator: 5.5.0
  - provisioning_api: 1.19.0
  - recommendations: 2.1.0
  - related_resources: 1.4.0
  - serverinfo: 1.19.0
  - settings: 1.12.0
  - sharebymail: 1.19.0
  - support: 1.12.0
  - tasks: 0.16.0
  - text: 3.10.1
  - theming: 2.4.0
  - theming_customcss: 1.16.0
  - twofactor_backupcodes: 1.18.0
  - updatenotification: 1.19.1
  - user_ldap: 1.20.0
  - user_status: 1.9.0
  - viewer: 2.3.0
  - workflowengine: 2.11.0
Disabled:
  - admin_audit: 1.19.0
  - circles: 29.0.0-dev (installed 26.0.0)
  - comments: 1.19.0 (installed 1.10.0)
  - contactsinteraction: 1.10.0 (installed 1.7.0)
  - encryption: 2.17.0
  - files_external: 1.21.0
  - files_pdfviewer: 2.10.0 (installed 2.0.1)
  - files_reminders: 1.2.0 (installed 1.0.0)
  - firstrunwizard: 2.18.0 (installed 2.15.0)
  - photos: 2.5.0 (installed 1.2.1)
  - privacy: 1.13.0 (installed 1.11.0)
  - survey_client: 1.17.0 (installed 1.15.0)
  - suspicious_login: 7.0.0
  - systemtags: 1.19.0 (installed 1.10.0)
  - twofactor_totp: 11.0.0-dev
  - weather_status: 1.9.0 (installed 1.0.0)

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

No response

Additional info

No response

The text was updated successfully, but these errors were encountered:

joshtrichards · 2024-07-09T22:28:44Z

If there is a 500 error, there should be a corresponding entry your nextcloud.log. That contains the stack trace. Do you happen to have that?

nagmat84 · 2024-07-10T06:34:30Z

Unfortunately not anymore.

Let's hope that the error happens again soon and then I will dump the corresponding log entry.

The error is a little bit difficult to (re-)trigger manually. A proper CalDAV client typically does not attempt to send those inconsistent VCALENDAR entries as those errors are already caught on the UI level and never reach the NC server. However, once every two months one of my five users (family) is able to create such an entry.

Alternatively, one would need a CalDAV client implementation for testing purposes which allows to send those inconsistent VCALENDAR entries deliberately. I had hoped that the NC test suite might be able to do that in order to provoke the error.

Alternatively, the NC error message "This recurrence rule does not generate any valid instances" should be somewhere in the code and easy to find. It seems to be a rather specific message. Maybe one can go from there and see what leads to the 500 error code.

joshtrichards · 2024-07-10T14:56:49Z

Related: #30514 & #5641

SebastianKrupinski · 2024-07-18T01:14:58Z

Duplicate of #30514

nagmat84 added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Jul 9, 2024

szaimen added the 29-feedback label Jul 9, 2024

joshtrichards added the feature: caldav Related to CalDAV internals label Jul 9, 2024

SebastianKrupinski marked this as a duplicate of #30514 Jul 18, 2024

SebastianKrupinski closed this as completed Jul 18, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug]: NC replies with HTTP status code 500 instead of 4xx when uploading invalid CalDAV entries. #46380

[Bug]: NC replies with HTTP status code 500 instead of 4xx when uploading invalid CalDAV entries. #46380

nagmat84 commented Jul 9, 2024 •

edited

Loading

joshtrichards commented Jul 9, 2024

nagmat84 commented Jul 10, 2024

joshtrichards commented Jul 10, 2024

SebastianKrupinski commented Jul 18, 2024

[Bug]: NC replies with HTTP status code 500 instead of 4xx when uploading invalid CalDAV entries. #46380

[Bug]: NC replies with HTTP status code 500 instead of 4xx when uploading invalid CalDAV entries. #46380

Comments

nagmat84 commented Jul 9, 2024 • edited Loading

⚠️ This issue respects the following points: ⚠️

Bug description

Steps to reproduce

Expected behavior

Installation method

Nextcloud Server version

Operating system

PHP engine version

Web server

Database engine version

Is this bug present after an update or on a fresh install?

Are you using the Nextcloud Server Encryption module?

What user-backends are you using?

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

joshtrichards commented Jul 9, 2024

nagmat84 commented Jul 10, 2024

joshtrichards commented Jul 10, 2024

SebastianKrupinski commented Jul 18, 2024

nagmat84 commented Jul 9, 2024 •

edited

Loading