Closed (fixed)
Project:
Event
Version:
5.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
22 Jan 2007 at 22:54 UTC
Updated:
28 Feb 2007 at 11:30 UTC
Jump to comment: Most recent file
The webcal links aren't useful to most people. What do people think abotu changing them to http links? If you agree please indicate if this change should be made in bith the 4.7 and the D5 version.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | event_no_webcal.patch | 553 bytes | HorsePunchKid |
Comments
Comment #1
deviantintegral commentedWhat clients don't pick up on the webcal link? I know that both OS X and KDE deal with it properly. Would such clients still behave the same with an http link?
Comment #2
killes@www.drop.org commentedfirefox on Linux doesn't pick it up for me. I have no idea what other clients do, but since we sent the correct mime type, I don#t see why they should complain. maybe try it on a site of yours?
Comment #3
HorsePunchKid commentedFirefox on Windows doesn't know what to do with webcal links by default. However, setting the content type is enough for it to at least try to spawn your iCalendar-associated application. I second killing the webcal substitution, unless those browsers that do understand it don't understand the content type header correctly. Attached patch removes the call.
Comment #4
killes@www.drop.org commentedapplied a similar patch.
Comment #5
dwgumby commentedThis change is a bit of a problem for me. I'm converting our Macintosh Users Group site to Drupal and a webcal link works much better, when its clicked iCal auto-launches and prompts to subscribe to the feed. With "http" the link instead downloads as an .ics document.
I can edit the module source code back to webcal but would it make sense to make this a module setting rather than hard-coding it one way or the other?
Comment #6
killes@www.drop.org commentedCan you check which MIME type is used for the ics file?
Comment #7
dwgumby commentedIts being served as text/calendar which I believe is correct. Here are the headers:
HTTP/1.1 200 OK
Date: Tue, 13 Feb 2007 19:40:43 GMT
Server: Apache/1.3.37 (Unix) mod_fastcgi/2.4.2 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a PHP-CGI/0.1b
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-Disposition: attachment; filename="calendar.ics";
Expires: Sun, 19 Nov 1978 05:00:00 GMT
X-Powered-By: PHP/4.4.4
Set-Cookie: PHPSESSID=d2b95084543c16ed14268145eef60f49; expires=Thu, 08 Mar 2007 23:14:03 GMT; path=/; domain=.acamug.org
Cache-Control: max-age=1209600
Expires: Tue, 27 Feb 2007 19:40:43 GMT
Last-Modified: Tue, 13 Feb 2007 19:40:43 GMT
Connection: close
Content-Type: text/calendar; charset=utf-8
The problem is that, even with the correct MIME type, with the http: protocol Safari will download the calendar file then launch iCal with the downloaded file rather than the original URL. The only way to pass the URL directly to iCal so it can subscribe to the feed is to use the webcal: protocol.
Comment #8
killes@www.drop.org commentedWell, with the webdav prefix the ical link is totally unusable for the average firefox user, no idea about IE. Since firefox users are more abundant then Safari users I'll leave it at that. Even setting the link conditional based on the requesting user's browser won't be too useful due to cachingfor anon users.
Comment #9
(not verified) commented