View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001264 | SOGo | Backend Calendar | public | 2011-04-14 15:09 | 2012-09-19 13:11 |
Reporter | dgp | Assigned To | ludovic | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 1.3.6 | ||||
Summary | 0001264: CalDAV PUT of an externally generated invite does not generate a valid REPLY object | ||||
Description | PUT an invite generated by an external calendar client into SOGo and it sends a reply to the organizer, however this is not a REPLY object, it's a direct copy of the original input (including other attendees). I'd expect to see a REPLY object generated based on the PUT data sent to the organizer only containing the one ATTENDEE component. | ||||
Additional Information | Steps:
SOGo then sends a message to the organizer saying "%USER% has not yet decided upon your event invitation" with the original invite as a text/calendar attachment. More telling is the RFC invalid "method=;" in the attachment's header: | ||||
Tags | No tags attached. | ||||
Why would you remove the METHOD line? Doing this, you're altering SOGo's data without its knowledge and this may lead to strange behaviors. If organizer A invites user B to an event, B isn't supposed to be able to add attendees to that event. B is supposed to be able to change its participation status, that's it. |
|
Maybe I was reading the RFC wrong. Watching other clients do PUT events, they didn't include a METHOD line. Not removing the METHOD line just causes SOGo to reply to the organiser including the original invite as an attachment and mime content-type method=REQUEST. I was hoping for a REPLY object to be attached. When the attendee's PARTSTAT=NEEDS-ACTION the text attachment says "$attendee has not yet decided upon your event invitation." If PARTSTAT=ACCEPTED the text says "$attendee has accepted your event invitation." I'm not sure if this really is a SOGo bug or user error. I got around the issue by doing it Properly client side. If the event doesn't already exist in SOGo: set SCHEDULE-AGENT=CLIENT on the organizer property and then generate the REPLY myself. |
|
Please retest with upcoming nightly builds (will be available in about 16 hours from now). |
|
I've just repeated the testing with debian-nightly squeeze version 1.3.0.20110711. I can't see any change in the originally reported behaviour. |
|
Is this bug still relevant? |
|
No feedback provided in months, closing. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2011-04-14 15:09 | dgp | New Issue | |
2011-06-15 20:55 | ludovic | Status | new => assigned |
2011-06-15 20:55 | ludovic | Assigned To | => ludovic |
2011-06-15 20:55 | ludovic | Target Version | => 1.3.8 |
2011-06-20 20:15 | ludovic | Note Added: 0002609 | |
2011-06-21 10:32 | dgp | Note Added: 0002612 | |
2011-07-05 17:21 | ludovic | Note Added: 0002657 | |
2011-07-05 17:55 | ludovic | Target Version | 1.3.8 => |
2011-07-12 16:08 | dgp | Note Added: 0002693 | |
2012-07-16 20:29 | ludovic | Note Added: 0004164 | |
2012-07-16 20:29 | ludovic | Status | assigned => feedback |
2012-09-19 13:11 | ludovic | Note Added: 0004488 | |
2012-09-19 13:11 | ludovic | Status | feedback => closed |
2012-09-19 13:11 | ludovic | Resolution | open => unable to reproduce |