Hi, 2011/4/27 christian.posta <christian.po...@gmail.com>
> You're trying to cache a pdf file/attachment? why? What's the purpose > of trying to do it that way? Why don't you just send it to the client when they ask for it? > Well, basically the reason is, that I want to show a progress dialog or "meanwhile" dialog to the user, cause the pdf is created on demand and this can take between 2-60 seconds, depending on the complexy of the newspaper page. Yes, I can provide a simple download link and let the browser show its wait cursor. But sadly, this is not enough for my users. So, I was looking into possible solutions. As you can't download anything via ajax directly, you have to trick the browser into caching it and then "download" the cached version. Currently, I am looking into a solution based on a onload event listener. > Also, there's no way on the server to 'force' content to be cached on > the client. The browser has to specifically allow it. All I can think > of is the browser needs to set if_modified_since headers in the > request for the server to respond with a 304, but I've never tried to > cache a pdf file or attachment. > Already tried it, and it hasn't worked at all. Best regards, Oliver -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
