Re: HTTP as OCP transport, ICAP/2.0

On Tue, 22 Apr 2003, The Purple Streak, Hilarie Orman wrote:

> I thought BEEP's security was the same as HTTP's: use TLS.
My understanding is that BEEP can _negotiate_ security profile for a
BEEP session (so that we do not have to worry about that at all).
Please correct me if I am wrong.

I know that HTTP has no idea it is being (or can be) wrapped with TLS.
Thus, we, as OCP writers, would have to worry about negotiating and
then enabling TLS.

Alex.