Gianni Johansson wrote:
Not to be picky, but fproxy does not support proper caching of documents on browser side. All fproxy does is prevent caching of already *non-cached* redirects (atleast according to HTTP/1.1 specification). If you wish, you can read up on other issues in the HTTP/1.1 thread presented here while back.- it doesn't set caching headers like fproxy yet.
_______________________________________________
devl mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
