caching and https / pw authorized pages

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 17 September 2002 02:27 pm, Dirk Mueller wrote:
> Hi,
>
> I've finally debugged the slowness of khtml on https and pw authorized
> pages and found out that kio-http doesn't allow caching of such pages.
> while I agree that this might be a security problem if they end up on disk,
> I think we should still be able to cache them in memory, at least till the
> browser window is closed.
>
> otherwise browsing password protected pages (like webbased administrative
> pages) is very very slow, because every image, every stylesheet and
> similiar is fetched on every pageview.

For SSL we only do not cache "text/*" objects but we do cache images. We can 
do the same for sites that require authentication. If you think it helps, I 
can also allow caching of css and javascript. I at least assume that those 
will in general not contain very sensitive information.

(If the webserver really doesn't want them to end up in the cache it should 
send along a no-cache directive)

Cheers,
Waldo
- -- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9h6KkN4pvrENfboIRAn5CAJ9b1gAmc/i3qsfVOb6Vp9EY9RsiOgCgoVYa
LsvZALpDdvERisSiLdCfXrU=
=qpBu
-----END PGP SIGNATURE-----