harik at chaos.ao.net writes: > ETag is just a string, so the base64-encoded key of the current file > would do nicely (for key responses)
If fproxy can get at the CHKs of content it is showing that's a possibility. > > My current caching target are the web interface images (and static > > pages), as these make most sense to cache. For freenet content, I > > don't know, we may actualy want to actively prevent caching. > > No, setting a reasonable Expires: time is a lot more friendly. I was alluding to the fact that some freenet content may be dangerous for you to have lying around in your browser cache. The safe choice would be to mark everything as uncacheable, and use your local store as a (slower) cache. I guess this can be a preference so the users can make this performance/security tradeoff themselves. -- Robbe -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.ng Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20021109/76ab5b37/attachment.pgp>
