[cosmo-dev] Re: Lightning + Cosmo

[Grant Baillie]

On 20 Dec, 2007, at 04:58, Alan Lord wrote:

> Jared Rhine wrote:
>>> I am using Thunderbird/Lightning...
>> Which version are you running?
>> There are bugs in Lightning 0.7 which are fixed in Mozilla's trunk/ 
>> nightlies that behave like you describe.
>> In general, one of the best ways to figure out what's really going  
>> on is to use a network packet sniffer to capture the CalDAV  
>> traffic.  You can often see errors/message returned by servers  
>> which are not displayed by clients.  Also check the Cosmo logs; the  
>> issue I'm thinking of above (DTEND+DURATION) should generate a  
>> compliant by Cosmo.  If not in the server log, then in the access  
>> logs (HTTP response codes of 4xx or 5xx can signify error  
>> conditions.)
>> -- Jared
>
> Hi Jared,
>
> I got a trace from Wireshark (saved in pdml and attached. I have  
> edited the file to hide my password). The error is a 403 Forbidden  
> message that Cosmo sends back and the description of the problem in  
> the xml is:
>
> Calendar data of type text/calendar, charset=utf-8 not allowed; only  
> text/calendar
>
> Does this make sense? Is Lightning not specifying the correct  
> charset or should Cosmo accept it?

Cosmo should accept that charset parameter IMO. Most clients omit it,  
so I'm guessing Cosmo doesn't deal with the case of parameters in the  
Content-Type header.

--Grant