[cosmo-dev] Re: Lightning + Cosmo

[Alan Lord]

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?

Thanks

Alan

-- 
The way out is open!
http://www.theopensourcerer.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cosmo_trace
Type: text/xml
Size: 59351 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20071220/84ae78cc/cosmo_trace.bin