Do you have caching set up for static files in your appengine-web.xml? This
can mean that when you deploy a new version the old scripts are still served
for a while. You can verify what scripts are available on the server by
requesting them directly in your browser.
--
You received this mess
On 5 zář, 01:35, Minehiko Ohya wrote:
> I když je nasazena aplikace, která pracuje normálně v místní
> do App Engine pro Google, nefunguje normálně na server. Já
> zjistil, že up-naložený JavaScript soubor nebyl nalezen z protokolu
> Administration Console, a že to nefunguje normálně. Prosím
> i
Thank you, Mr. John Patterson.
I don't have caching set up, but I found the cause of this problem
with your advice. That is as followings.
I reviewed appengine-web.xml, and found that the JavaScript file was
defined as "static-files" in it. So, I changed it to "resource-files",
and deployed the
Thank you of your response, Mr. John Patterson.
I think the cause of this problem isn't caching by the following
reason. From the beginning of deploying, this application hasn't been
able to find the JavaScript file, so, any JavaScript file hasn't been
cached.
I think, the cause of this probl
On 07/09/2011 07:19, Minehiko Ohya wrote:
I reviewed appengine-web.xml, and found that the JavaScript file was
defined as "static-files" in it.
I should have been more clear - that's what I meant by caching. For
static resources you specify the length of time you want Google to cache
it for
