Tickets :: [#10739] Empty response to REPORT may lead to crash

Summary	Empty response to REPORT may lead to crash
Queue	Kronolith
Queue Version	3.0.11
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	christof (at) buergi (dot) lugs (dot) ch
Created	11/12/2011 (4991 days ago)
Due
Updated	11/30/2011 (4973 days ago)
Assigned
Resolved	11/30/2011 (4973 days ago)
Github Issue Link
Github Pull Request
Milestone	3.0.13
Patch	Yes

11/30/2011 06:35:06 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Resolved Milestone ⇒ 3.0.13

11/30/2011 06:34:42 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git for this ticket: [jan] Don't fail on empty CalDAV calendars (christof@buergi.lugs.ch, ~~Bug #10739~~). 3 files changed, 7 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/39a0d24e2a4c3c688475692957351b8a12c3c163

11/12/2011 05:52:18 PM	christof (at) buergi (dot) lugs (dot) ch	Comment #1 Priority ⇒ 2. Medium New Attachment: Ical.patch Patch ⇒ Yes Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ Empty response to REPORT may lead to crash Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
When sending a REPORT request to an empty calendar, an empty <response> tag may be returned (at least Google Calendar does so). This leads to Kronolith crashing when it tries to access the nonexistant <propstat> sub tag. This patch adds an extra check, whether there is a <propstat> inside the <response> in the first place.