[Tickets #13822] Shared calendar makes CalDAV fail with 500

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13822
------------------------------------------------------------------------------
  Ticket             | 13822
  Created By         | skhorde at smail.inf.fh-bonn-rhein-sieg.de
  Summary            | Shared calendar makes CalDAV fail with 500
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


skhorde at smail.inf.fh-bonn-rhein-sieg.de (2015-01-22 10:59) wrote:

On the Webpage an user has one own and four shared calendars and the  
user's tasks. I see the data (pencil icon) of all calendars except  
one. The latter shows "You are not allowed to see this calendar."   A  
CalDAV client queries the principal of an user and gets 6 shares, all  
prefixes by <URL>rpc.php/calendars/<user>/

calendar:1
calendar:2
calendar:3
calendar~4
calendar~5
tasks~6

Calemdars 1 and 2 are public ones, 3 and 5 and shared ones from  
another user, 4 and 6 are ones from the user itself.

All calendars except 5 are working as expected. The requests to  
calendar 5 result in "500 Internal server error". A webdav client  
shows the same.

The calendar 5 has been accidently shared as "Object Creator 	x Show  
	x Read 	x Edit 	x Delete", everything else is unchecked, no user  
configuered.

The annoying thing here is the 500 http error code for the CalDAV  
client, because it displays a warning each retry time. IMHO, if the  
calendar is shared and visible to the user, the user should get access  
to its metadata / container / whatever, but not necessarily to the  
events, hence, neither the GUI nor CalDAV should get an error.

Maybe related to bug #12380 .