Summary | Access to certain CalDAV servers fails due to XML namespace problems |
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/05/2011 (4993 days ago) |
Due | |
Updated | 11/07/2011 (4991 days ago) |
Assigned | |
Resolved | 11/07/2011 (4991 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | 3.0.12 |
Patch | Yes |
State ⇒ Resolved
Milestone ⇒ 3.0.12
Specify namespace when parsing CalDAV response
(christof@buergi.lugs.ch,
Bug #10716).I still can't get Google CalDAV working though.
3 files changed, 10 insertions(+), 6 deletions(-)
http://git.horde.org/horde-git/-/commit/90ff2918cd010344ef89653162e3f2c7784c25f4
Priority ⇒ 2. Medium
New Attachment: Ical.php.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Access to certain CalDAV servers fails due to XML namespace problems
Type ⇒ Bug
State ⇒ Unconfirmed
PROPFIND and REPORT, that "DAV:" is declared as default namespace.
This is not necessarily so.
Many servers use prefixes instead. I confirmed this behaviour for
SabreDAV and Google Calendar. The patch I attached makes the XML query
aware of the namespace, and thus should work whether "DAV:" is
declared as default namespace or as a prefix.