Apple iCal & cosmo-demo

I just discovered that Apple iCal doesn't support HTTPS,
which means  
it won't work with our https://cosmo-d
emo.osafoundation.org/ server.   
I guess when we tested this earlier we weren't using HTTPS
(or else  
iCal stopped supporting HTTPS).  Is this something we should
 
address?  It's a shame to go through all this work to allow
non- 
Chandler clients to interoperate with us, and then have it
not work.

Or am I the only one having trouble subscribing to a
cosmo-demo  
collection with my iCal?

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

On Mar 2, 2006, at 13:59 , Morgen Sagen wrote:

> I just discovered that Apple iCal doesn't support
HTTPS, which  
> means it won't work with our https://cosmo-d
emo.osafoundation.org/  
> server.  I guess when we tested this earlier we
weren't using HTTPS  
> (or else iCal stopped supporting HTTPS).  Is this
something we  
> should address?  It's a shame to go through all this
work to allow  
> non-Chandler clients to interoperate with us, and then
have it not  
> work.
>
> Or am I the only one having trouble subscribing to a
cosmo-demo  
> collection with my iCal?

It doesn't work for me, either, on 10.4.4. Poking around in
Google,  
it seems we're not the only ones. It looks as if they had
some  
certificate-related problems with https in the past, so
maybe that's  
why it got turned off.

There's a horrible nasty workaround (involving stunnel)
here:

<http://rul
ink.rutgers.edu/macical.html>

--Grant

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

On 3/2/06, Morgen Sagen <morgenosafoundation.org>
wrote:

> Or am I the only one having trouble subscribing to a
cosmo-demo
> collection with my iCal?

hm, i'm not sure that i ever tried it against
cosmo-demo:443 specifically ;)

if it really is the case that ical can't do ssl, and that
isn't going
to change anytime soon, then perhaps we should reconsider
our ssl-only
policy for cosmo-demo.
_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

I had trouble too.

On Mar 2, 2006, at 1:59 PM, Morgen Sagen wrote:

> I just discovered that Apple iCal doesn't support
HTTPS, which  
> means it won't work with our https://cosmo-d
emo.osafoundation.org/  
> server.  I guess when we tested this earlier we
weren't using HTTPS  
> (or else iCal stopped supporting HTTPS).  Is this
something we  
> should address?  It's a shame to go through all this
work to allow  
> non-Chandler clients to interoperate with us, and then
have it not  
> work.
>
> Or am I the only one having trouble subscribing to a
cosmo-demo  
> collection with my iCal?
>
> ~morgen
> _______________________________________________
> Cosmo mailing list
> Cosmoosafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo

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

Yup. Me too. So I deleted the 'S' in HTTPS and it worked.
-Priscilla

On Mar 3, 2006, at 12:21 PM, Mimi Yin wrote:

> I had trouble too.
>
> On Mar 2, 2006, at 1:59 PM, Morgen Sagen wrote:
>
>> I just discovered that Apple iCal doesn't support
HTTPS, which  
>> means it won't work with our https://cosmo-d
emo.osafoundation.org/  
>> server.  I guess when we tested this earlier we
weren't using  
>> HTTPS (or else iCal stopped supporting HTTPS).  Is
this something  
>> we should address?  It's a shame to go through all
this work to  
>> allow non-Chandler clients to interoperate with us,
and then have  
>> it not work.
>>
>> Or am I the only one having trouble subscribing to
a cosmo-demo  
>> collection with my iCal?
>>
>> ~morgen
>> _______________________________________________
>> Cosmo mailing list
>> Cosmoosafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo
>
> _______________________________________________
> Cosmo mailing list
> Cosmoosafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo

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

So it seems like we do need to spit out a separate URL for
iCal  
users? Morgen?

Mimi

On Mar 6, 2006, at 10:41 AM, Priscilla Chung wrote:

> Yup. Me too. So I deleted the 'S' in HTTPS and it
worked. -Priscilla
>
> On Mar 3, 2006, at 12:21 PM, Mimi Yin wrote:
>
>> I had trouble too.
>>
>> On Mar 2, 2006, at 1:59 PM, Morgen Sagen wrote:
>>
>>> I just discovered that Apple iCal doesn't
support HTTPS, which  
>>> means it won't work with our https://cosmo- 
>>> demo.osafoundation.org/ server.  I guess when
we tested this  
>>> earlier we weren't using HTTPS (or else iCal
stopped supporting  
>>> HTTPS).  Is this something we should address? 
It's a shame to go  
>>> through all this work to allow non-Chandler
clients to  
>>> interoperate with us, and then have it not
work.
>>>
>>> Or am I the only one having trouble subscribing
to a cosmo-demo  
>>> collection with my iCal?
>>>
>>> ~morgen
>>> _______________________________________________
>>> Cosmo mailing list
>>> Cosmoosafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/cosmo
>>
>> _______________________________________________
>> Cosmo mailing list
>> Cosmoosafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo
>

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

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.

On Mar 6, 2006, at 11:59 AM, Mimi Yin wrote:

> So it seems like we do need to spit out a separate URL
for iCal  
> users? Morgen?
>
> Mimi
>
> On Mar 6, 2006, at 10:41 AM, Priscilla Chung wrote:
>
>> Yup. Me too. So I deleted the 'S' in HTTPS and it
worked. -Priscilla
>>
>> On Mar 3, 2006, at 12:21 PM, Mimi Yin wrote:
>>
>>> I had trouble too.
>>>
>>> On Mar 2, 2006, at 1:59 PM, Morgen Sagen wrote:
>>>
>>>> I just discovered that Apple iCal doesn't
support HTTPS, which  
>>>> means it won't work with our https://cosmo- 
>>>> demo.osafoundation.org/ server.  I guess
when we tested this  
>>>> earlier we weren't using HTTPS (or else
iCal stopped supporting  
>>>> HTTPS).  Is this something we should
address?  It's a shame to  
>>>> go through all this work to allow
non-Chandler clients to  
>>>> interoperate with us, and then have it not
work.

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

On 3/6/06, Morgen Sagen <morgenosafoundation.org>
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.

i agree. might be useful to have a section on the cosmo-demo
welcome
page about client compatibility, or at least links to the
(yet to be
written) cosmo client config docs.
_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

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.

+1.  The server might be able to tell you which URLs are
direct  
mappings of each other, but it's harmful to
interoperability for the  
client to make an assumption like this about mappings.

Lisa

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

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. Hmm... reminds me of web page development
for 
IE/Firefox computability 



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