[Seaside] RE: iCal to Drupal requires Content-Encoding: gzip
boris at deepcovelabs.com
Tue Sep 22 18:11:59 UTC 2009
Are you sure its actually utf8? I had to put some nasty hacks in VW/Seaside to get that to work in both 7.6 and 7.7... Just a thought, if your content is all ascii then it makes no difference.
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside List <seaside at lists.squeakfoundation.org>
Sent: Tue Sep 22 11:04:27 2009
Subject: [Seaside] RE: iCal to Drupal requires Content-Encoding: gzip
>>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
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
Drupal is still not happy. But at least this looks cleaner than what I had before.
A bit more to do.
seaside mailing list
seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside