On Mon, Oct 03, 2011 at 05:05:13PM +0200, Stephan Beal wrote:
> 2011/10/3 Lluís Batlle i Rossell <virik...@gmail.com>
>
> > What would happen if JSON answers had not 'no-store'? Would not be
> > 'no-cache'
> > enough? It should be up to the json clients though.
> >
>
> Sorry, my mistake - i meant no-cache, not no-store.
So, as I tested, removing 'no-store' makes firefox remember the form in the case
of back-forward in history. But clicking to the same url makes firefox still
refetch the page contents.
I think that's exactly what I want. Anyone against?
(Looking for 'chrome no-store' in google quite a lot of bug reports, for what
I've seen)
Index: src/cgi.c
===================================================================
--- src/cgi.c
+++ src/cgi.c
@@ -325,11 +325,11 @@
*/
/*time_t expires = time(0) +
atoi(db_config("constant_expires","604800"));*/
time_t expires = time(0) + 604800;
fprintf(g.httpOut, "Expires: %s\r\n", cgi_rfc822_datestamp(expires));
}else{
- fprintf(g.httpOut, "Cache-control: no-cache, no-store\r\n");
+ fprintf(g.httpOut, "Cache-control: no-cache\r\n");
}
/* Content intended for logged in users should only be cached in
** the browser, not some shared location.
*/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
