It seems to me that when you have low (in general, hacker terms) quotas (I'm talking about the free GAE plan) and rather large files that you want to transfer to your users, you somehow protect thouse files from "bad" users
So sad
By default, App Engine makes all files in WAR accessible as static files except for JSP and files in WEB-INF /. Any request a URL whose path matches the static file serves the file directly to the browser, even if the path matches the servlet or filter mapping.match of the servlet or filter.
what is short in implementing folder protection methods inside a WAR? (code, examples, examples of articles, etc.)
(situation: we use GAE for Java, so we just program JSP and Java and xml, JS and Html. So: an empty gae project, there is no source (only default html) in the data folder in this war with some files, which should not fall into bad hands)
Rella source
share