Re: [Evolution-hackers] Attachments?

[Adam Tauno Williams <awilliam opengroupware us>]

On Thu, 2011-06-23 at 22:00 -0400, Adam Tauno Williams wrote:
> On Thu, 2011-06-23 at 11:23 -0400, Adam Tauno Williams wrote:
> > Are attachments for tasks related to a CalDAV task list supposed to be
> > functional?
> > If the attachment is encoded as a link [and the site requires
> > authentication] Evolution presents a "HTTP authentication required"
> > error dialog and drops the attachment;  it doesn't ask for
> > authentication or attempt to use the credentials used for the CalDAV
> > server
> > If the attachment is encoded as binary [present in the VTODO] it simply
> > fails with an "operation not supported" message
> > Evolution 2.32.1
> I've managed to encode the attachments in such a way that they do not
> raise any error when the task is viewed in Evolution;  however the
> attachments simply do not appear.  I've verified in wireshark that the
> attachments are received by Evolution.

Progress!  Sort of.  I upgraded to Evolution 3.0.2 [openSUSE 11.4 x64
using the GNOME  repo].

With this version the attachments appear, with names.  Looks great.  But
the contents of the attachment when I open it are.... base64 text.
Evolution is not decoding from base64 back to the files actual content?

I dug the X-EVOLUTION-CALDAV-ATTACHMENT-NAME property out of the
Evolution source code.

> HTTP/1.1 200 OK
> Server: BaseHTTP/0.3 Python/2.7
> Date: Fri, 24 Jun 2011 01:55:06 GMT
> Content-Length: 751475
> Content-Type: text/calendar
> ETag: 18092560:15
> Connection: close
> 
> BEGIN:VCALENDAR
> VERSION:2.0
> PRODID:-//PYVOBJECT//NONSGML Version 1//EN
> BEGIN:VTODO
> ATTACH;X-ORACLE-FILENAME=OGo18215321.ods;FMTTYPE=application/octet-stream;
> ENCODING=BASE64;VALUE=BINARY;X-COILS-FILENAME=OGo18215321.ods;X-EVOLUTION-
>  CALDAV-ATTACHMENT-NAME=OGo18215321.ods:VUVzREJCUUFBQWdBQUNkMnF6NkZ
>  iRG1LTGdBQUFDNEFBQUFJQUFBQWJXbHRaWFI1Y0dWaGNIQnNhV05oZEdsdmJpOTJibVF1
>  YjJGegphWE11Y.....