Hallöchen!
Torsten Bronger writes:
> We've programmed a Django app with mandatory login. Under
> somewhat obscure circumstances, the browser (Firefox and Chrome)
> sends spurious If-Modified-Since header fields and may take the
> page of another user from the browser cache. [...]
>
> [...]
>
> The big question is: Why does the browser send the
> If-Modified-Since in (*****).
>
> And the even bigger question is: How can be prevent it?
Some Internet research revealed that browsers don't really care
about the Vary field. It is used primarily by cache servers. A
workaround is to send an Etag which consists of (a hash of) the
timestamp and the user ID.
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
