[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev '\' reloading documents
From: |
Leonid Pauzner |
Subject: |
Re: lynx-dev '\' reloading documents |
Date: |
Fri, 30 May 2003 09:38:35 +0400 (MSD) |
29-May-2003 08:06 Doug Kaufman wrote:
> On Thu, 29 May 2003, Ian Collier wrote:
>> But I've already got the document - if anything was confidential then
>> it's too late! No one else is going to see it if it's only cached in
>> memory.
> But it isn't only cached to memory. SOURCE_CACHE can be set to "FILE".
> If we are to cache secure documents, we should make sure that the file
> is as secure as is reasonably possible.
Yes. But while we are talking to https the secure content is _usually_ sent
in a single direction, from client to server (POST data, with passwords
etc.), so it will not be compromised by source_cache. Though it is perfectly
valid to send secure content in the other direction...
> Doug
> --
> Doug Kaufman
> Internet: address@hidden
> ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
Re: lynx-dev '\' reloading documents, Chuck Martin, 2003/05/29
Re: lynx-dev '\' reloading documents, Henry Nelson, 2003/05/28
Re: lynx-dev '\' reloading documents, Henry Nelson, 2003/05/29
Re: lynx-dev '\' reloading documents, Henry Nelson, 2003/05/29
Re: lynx-dev '\' reloading documents, Henry Nelson, 2003/05/29
Re: lynx-dev '\' reloading documents, Henry Nelson, 2003/05/30