List Info

Thread: Apple iCal & cosmo-demo
Apple iCal & cosmo-demo
user name
 2006-03-07 18:53:38 

  


  

    
Found an interesting note at <http://rulink.rutgers.edu/macical.html>, relating how to use https links with iCal:

To do things this way you need to specify a URL such as https://rulink.rutgers.edu/cgi-bin/subscribe?user=MYUSER&pass=MYPASS&;CALID.ics where you replace MYUSER with your username (NetID), MYPASS with your password, and CALID with your calendar ID (normally your NetID). (Note that & should be represented as &amp; in the file.) Unfortunately the iCal application does not accept https:. The problem is in the user interface, not the application. So you'll need to edit the configuration file produced by the application.
The application won't let you create a URL with https: in it, so initially, add the calendar without login, using the URL http://rulink.rutgers.edu/cgi-bin/subscribe?CALID.ics
If you need to login in order to see the calendar, iCal will initially see no data.
Now edit the file ~/Library/Preferences/com.apple.iCal.sources.plist. You will find an entry that looks like this:
<dict&gt;
<key>;Last Successful Slurp Date</key>
<string>06/06/03 00:27:11&lt;/string&gt;
<key>;baseURL<;/key>
<key>;filtering mask</key>
<integer>3</integer>
<key>;use iTools</key>
<false/>
You need to make two changes:
So the two lines for the URL will end up looking like this:
<key>;baseURL<;/key>
If your password happens to have an ampersand in it, you will want to represent it as "%26" (without the quotes). You may also need to represent an equal sign by "%3D".

So the application *can* handle it - the UI just doesn't permit it. Weird.

Reid

On Mar 7, 2006, at 13:49, Morgen Sagen wrote:
On Mar 7, 2006, at 9:31 AM, Charles Wyble wrote:
Lisa Dusseault wrote:
 
On Mar 6, 2006, at 12:17 PM, Morgen Sagen wrote:
I don't think Chandler should assume that there will be a port 80 ('http') server along with the port 443 ('https') server, and that they both refer to the same Cosmo instance.  I'm not sure how Chandler could know this in a general way, without having site-specific logic (in other words, "if host == 'cosmo-demo' then port 443 is equivalent to 80") inside Chandler.  It's perhaps unusual that cosmo-demo is set up this way, and I wouldn't count on it.  I would be interested to hear what other people think.
 
Well this isn't entirely true. Its not Chandler thats the problem but Apple ICAL. They evidently don't support https. So the logic would actually need to be inside Cosmo no? To detect the client and do different things.
 

Well, yes and no.  It affects Chandler because we have a feature which allows you to copy a shared collection's URL to the clipboard so that you can paste it into either an email message (to invite someone to subscribe) or to another client (such as iCal).  The original question was if Chandler could somehow generate the 'iCal friendly' URL in this situation, and I think it's unfortunately 'no' since it's unlikely there *will* be such a non-HTTPS URL (although there happens to be one now on cosmo-demo, which was news to me).

It is really unfortunate Apple removed HTTPS support for iCal (which apparently happened quite recently).  I guess we have to ask ourselves if we want to just use regular HTTP (port 80) rather than HTTPS.


  

  
  
   
     
    

  

    Apple iCal & cosmo-demo
  


  

     user name

     2006-03-08 12:16:44
  


  

    
That's just broken - which reinforces the idea that this
whole thing  
is Apple's problem, not OSAF's. I suggested to Lisa that
somebody  
ought to talk to the iLife folks over at Apple about it.

- Oren

On Mar 7, 2006, at 10:53 AM, Reid Ellis wrote:

> Found an interesting note at <http://rulink.rutgers.edu/
 
> macical.html>, relating how to use https links with
iCal:
>
>> To do things this way you need to specify a URL
such as https:// 
>> rulink.rutgers.edu/cgi-bin/subscribe? 
>> user=MYUSER&pass=MYPASS&CALID.ics where you
replace MYUSER with  
>> your username (NetID), MYPASS with your password,
and CALID with  
>> your calendar ID (normally your NetID). (Note that
& should be  
>> represented as &amp; in the file.)
Unfortunately the iCal  
>> application does not accept https:. The problem is
in the user  
>> interface, not the application. So you'll need to
edit the  
>> configuration file produced by the application.
>>
>> The application won't let you create a URL with
https: in it, so  
>> initially, add the calendar without login, using
the URL http:// 
>> rulink.rutgers.edu/cgi-bin/subscribe?CALID.ics
>>
>> If you need to login in order to see the calendar,
iCal will  
>> initially see no data.
>>
>> Now edit the file ~/Library/Preferences/ 
>> com.apple.iCal.sources.plist. You will find an
entry that looks  
>> like this:
>>
>> <dict>
>> <key>Last Successful Slurp Date</key>
>> <string>06/06/03 00:27:11</string>
>> <key>baseURL</key>
>> <string>http://rulink.rutgers.edu/cgi-bin/subscribe?myname.ic
s</ 
>> string>
>> <key>filtering mask</key>
>> <integer>3</integer>
>> <key>use iTools</key>
>> <false/>
>> You need to make two changes:
>>
>> Change the URL from http://rulink.rutgers.edu to https:// 
>> rulink.rutgers.edu
>> Add your username and password
>> So the two lines for the URL will end up looking
like this:
>> <key>baseURL</key>
>> <string>https:/
/rulink.rutgers.edu/cgi-bin/subscribe? 
>>
user=MYUSER&amp;pass=MYPASS&amp;myname.ics</strin
g>
>> If your password happens to have an ampersand in
it, you will want  
>> to represent it as "%26" (without the
quotes). You may also need  
>> to represent an equal sign by "%3D".
>
> So the application *can* handle it - the UI just
doesn't permit it.  
> Weird.
>
> Reid
>
> On Mar 7, 2006, at 13:49, Morgen Sagen wrote:
>> On Mar 7, 2006, at 9:31 AM, Charles Wyble wrote:
>>> Lisa Dusseault wrote:
>>>> On Mar 6, 2006, at 12:17 PM, Morgen Sagen
wrote:
>>>>> I don't think Chandler should assume
that there will be a port  
>>>>> 80 ('http') server along with the
port 443 ('https') server,  
>>>>> and that they both refer to the same
Cosmo instance.  I'm not  
>>>>> sure how Chandler could know this in a
general way, without  
>>>>> having site-specific logic (in other
words, "if host == 'cosmo- 
>>>>> demo' then port 443 is equivalent to
80") inside Chandler.   
>>>>> It's perhaps unusual that cosmo-demo
is set up this way, and I  
>>>>> wouldn't count on it.  I would be
interested to hear what other  
>>>>> people think.
>>> Well this isn't entirely true. Its not
Chandler thats the problem  
>>> but Apple ICAL. They evidently don't support
https. So the logic  
>>> would actually need to be inside Cosmo no? To
detect the client  
>>> and do different things.
>>
>> Well, yes and no.  It affects Chandler because we
have a feature  
>> which allows you to copy a shared collection's URL
to the  
>> clipboard so that you can paste it into either an
email message  
>> (to invite someone to subscribe) or to another
client (such as  
>> iCal).  The original question was if Chandler could
somehow  
>> generate the 'iCal friendly' URL in this
situation, and I think  
>> it's unfortunately 'no' since it's unlikely
there *will* be such a  
>> non-HTTPS URL (although there happens to be one now
on cosmo-demo,  
>> which was news to me).
>>
>> It is really unfortunate Apple removed HTTPS
support for iCal  
>> (which apparently happened quite recently).  I
guess we have to  
>> ask ourselves if we want to just use regular HTTP
(port 80) rather  
>> than HTTPS.
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev"
mailing list
> h
ttp://lists.osafoundation.org/mailman/listinfo/dev

_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo


  


  

    
  

  
  
   
     
    






 [1-2]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )