[Seaside] RE: iCal to Drupal requires Content-Encoding: gzip

bobn at rogers.com bobn at rogers.com
Tue Sep 22 18:04:27 UTC 2009

>>By the way, it might be easier to compare text files obtained with curl,
>>curl -iL http://www.google.com > google.txt
>>curl -iL http://www.microsoft.com > microsoft.txt

>Yes, this does show the Content-Dispostion difference.  Google data is correctly in-lined.  Our data
>has the <!DOCTYPE hmtl... header. 
>Sounds like I need to understand how to properly answer the iCal datal.  I can work on that. 

 response := Seaside.WAResponse 
  document: self iCalText  
  mimeType:  'text/calendar;charset=utf-8'.
 response doNotCache.
 self session returnResponse: response.

...curl says were answering... 

HTTP/1.1 200 OK
Expires: Sat, 1 Jan 2095 07:00:00 -0500
Expires: Wed, 11 Jun 1980 08:00:00 -0400
Cache-control: no-cache,must-revalidate
Pragma: no-cache
Content-type: text/calendar;charset=utf-8
Content-length: 10944


Drupal is still not happy.  But at least this looks cleaner than what I had before.  
A bit more to do.


More information about the seaside mailing list