Like I said, I don't like the way it works either, but that was the gist of
the explanation I got from Macromedia.
It was a while ago, so I don't remember the exact details.
Spike
--------------------------------------------
Stephen Milligan
Code poet for hire
http://www.spike.org.uk
Do you cfeclipse? http://cfeclipse.tigris.org
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Jochem van Dieten
>Sent: Sunday, August 01, 2004 7:02 AM
>To: CF-Talk
>Subject: Re: Blackstone Presentation
>
>Spike wrote:
>> I believe it's done that way because that's how HTTP basic
>authentication
>> works.
> >
>> That allows you to use cflogin to authenticate a person who
>has already been
>> authenticated that way.
>
>That sounds the wrong way around.
>
>For cflogin to recycle HTTP Basic Authentication credentials, CF
>is only required to be able to read them. That does in no way
>require CF to recycle that very unsafe mechanism when it is
>setting its own cookies.
>
>Jochem
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
