0005282: rfc4791 freebusy request does not work - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0005282	SOGo	Backend Calendar	public	2021-03-13 20:48	2023-02-12 11:36

Reporter	tobixen	Assigned To
Priority	low	Severity	minor	Reproducibility	always
Status	new	Resolution	open
Product Version	5.0.1

Summary	0005282: rfc4791 freebusy request does not work
Description	I'm sending a report request that looks quite the same as the example in RFC 4791, section 7.10.1 - https://tools.ietf.org/html/rfc4791#section-7.10.1 - but I get a 501 error in return. The RFC states that ... Support for the CALDAV:free-busy-query REPORT is REQUIRED. Hence, this is a compatibility issue. (I sort of hope I've done something wrong on my side - very few caldav servers seems to support a freebusy-request as specified in RFC 4791. I'm aware that RFC 6638 specifies another way of doing freebusy-requests, but haven't gotten to test that one yet).
Steps To Reproduce	Throw up the ZEG. Do a REPORT request. URL used: http://192.168.56.101/SOGo/dav/sogo1/Calendar/pythoncaldav-test/ (the calendar was created prior to doing the test) Headers: User-Agent: Mozilla/5.0 Content-Type: application/xml; charset="utf-8" Accept: text/xml, text/calendar Depth: 1 Body: <?xml version='1.0' encoding='utf-8'?> <C:free-busy-query xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"> <C:time-range start="20070713T150000Z" end="20070715T150000Z"/></C:free-busy-query>
Tags	CalDAV

Date Modified	Username	Field
2021-03-13 20:48	tobixen	New Issue
2021-03-13 20:48	tobixen	Tag Attached: CalDAV
2023-02-12 11:36	tobixen	Note Added: 0016654

tobixen 2023-02-12 11:36 reporter ~0016654	Revisited this in 5.8.0, and it's still an issue. A minor issue, I suppose most people would rather use the freebusy requests as defined in RFC6638.