nextcloud / nextcloud/server

[Bug]: Many REPORT request to the user's scheduling inbox

Open
#40,855 0 comments 0 reactions 1 assignee View on GitHub

@ChristophWurst is already working on this.

Since Oct 10, 2023.

0. Needs triage 27-feedback bug feature: caldav performance 🚀
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description
123.321.123.321 - - [10/Oct/2023:13:01:26 +0000] "REPORT /remote.php/dav/calendars/usr/inbox/ HTTP/1.1" 401 1231 "-" "iOS/17.0.3 (21A360) dataaccessd/1.0" 90183
123.321.123.321 - - [10/Oct/2023:13:01:26 +0000] "REPORT /remote.php/dav/calendars/usr/inbox/ HTTP/1.1" 207 52784 "-" "iOS/17.0.3 (21A360) dataaccessd/1.0" 554370
123.321.123.321 - - [10/Oct/2023:13:01:27 +0000] "REPORT /remote.php/dav/calendars/usr/inbox/ HTTP/1.1" 401 1193 "-" "iOS/17.0.3 (21A360) dataaccessd/1.0" 218993
123.321.123.321 - - [10/Oct/2023:13:01:27 +0000] "REPORT /remote.php/dav/calendars/usr/inbox/ HTTP/1.1" 207 68910 "-" "iOS/17.0.3 (21A360) dataaccessd/1.0" 1020281
123.321.123.321 - - [10/Oct/2023:13:01:28 +0000] "REPORT /remote.php/dav/calendars/usr/inbox/ HTTP/1.1" 401 1193 "-" "iOS/17.0.3 (21A360) dataaccessd/1.0" 249884

This increases the server load.

For one user we observed 72 of those REPORT requests.

Steps to reproduce
  1. ???
Expected behavior

Normal load.

Installation method

None

Nextcloud Server version

27

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?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.