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

Philippe Marschall philippe.marschall at gmail.com
Mon Sep 21 18:14:15 UTC 2009

2009/9/21 Bob Nemec <bobn at rogers.com>:
> Hello,
> We're trying to provide an iCal feed from Seaside (on VW) to Drupal.


> The
> Drupal use of the feed can be tested using a Google calendar iCal feed, and
> it works fine.  We're able to produce a simple iCal document as well, but
> Drupal does not accept it.  Both the Google and our Seaside iCal feeds
> download fine with just the browser.
> The one big difference we can see in the header is that the Google contains
> 'Content-Encoding: gzip' and ours does not.  I have not be able to determine
> how we can properly provide the gzip compressed version of the content.

It is unlikely that Drupal needs the content as gzip. Have you
compared the actual data? Does the format and encoding match? Do you
use CR LR and not just LF or CR? Are you sure content-length matches
the lenght of your content? Have you tried returning the same thing as
Google just without gzip (and a correct content-lenght). Have you
tried dropping the content-disposition header? ...

> Has anyone done an iCal feed from Seaside to Drupal?

Not with Drupal.

> Or, how can I get the
> gzip properly to be properly supported in my data source?

I don't think this is your problem.


More information about the seaside mailing list