Hi there, I am trying to build an offline-django(1.6.5)-app (a single page for the beginning). I am serving a manifest-file with correct mime-type (text/cache-manifest), linking it with the <html>-tag, rendered in a template. The page is cached and shown offline in chrome, but not in IE11 nor Firefox (30). I guess the reason is the response-headers sent by django. They always include "Cache-Control: no-store, no-cache, must-revalidate" and pragma "no-cache" (for the view, not static files, which get cached). I am trying to get rid of these (for testing), but I cant't find a way... I tried the cache_control-decorator on dispatch-method of the view, setting the header in render_to_response and a middleware. No success. May be they are set by the web-server? They appear when served on dev-server or on apache/wsgi. Does anybody have an idea, how to modify/get rid of these headers - or getting an offline-site to work in IE11/FF? Thank you for any help!
That's what it should be: http://ie.microsoft.com/testdrive/HTML5/Cookbook/ - works in IE11, but not in FF (like many other public offline-html5-demos), so I think FF is buggy, regarding appcache?? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e46edec9-80b5-4567-957c-63f7b22da0f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
