CalDAV and iCal terminates with HTTP 500

Best practice information from Scalix users relating to integration of Scalix with other products.

Moderator: ScalixSupport

florian
Scalix
Scalix
Posts: 3852
Joined: Fri Dec 24, 2004 8:16 am
Location: Frankfurt, Germany
Contact:

Postby florian » Mon Mar 09, 2009 6:34 am

can you possibly try to export the object using sxmboxexp? (use omcontain to "r"ead the entry, obtain the Direct Reference ID, then use sxmboxexp --dref <dref> -F -a filename.exp) to write it to a file.

This will have richer information than the .ics export from the client.

Tx,
Florian
Florian von Kurnatowski, Die Harder!

gren
Scalix
Scalix
Posts: 264
Joined: Thu Mar 25, 2004 10:27 am
Contact:

Postby gren » Tue Mar 10, 2009 10:26 am

Hi Andreas,

Thanks for your help. As a result of the information you have provided, I believe I now know what the cause of the problem is and have logged a bug in our Bugzilla to track it. Please see :
https://bugzilla.scalix.com/show_bug.cgi?id=19346
to track progress.

Essentially, iCal.app choosed the filename for the entry in the Calendar based on the UID value used in the text/calendar body part of the message which has been sent. We do not handle that (correctly formed) filename properly after that if the filename contained URL escaping characters.

Regards,
Gren


Return to “Third Party Integration”



Who is online

Users browsing this forum: No registered users and 2 guests