Hi Guoshun,
It seems like a bug in your server, and still not something AngularJs can
fix fr you. I'm pretty sure there are settings for the server that can fix
this.
Another way to do cache-busting is to add a hash to every request. But that
makes things more complex.
Regards
Sander
--
You
Hi Sander,
I recently faced the same issue. After some digging, I finally found the
root cause is the modification date of template HTML files are too old. I
found that if your template files modified earlier than 1997-0726 05:00,
the issue would happen.
Note that my testing web server is
Hi Anne,
This is so much outside the reach of angular! A 304 means the server say's
to the browser, there is no change in this file, you can use your cached
version. They only way to get a 304 is when there is indeed a cached
version, otherwise, the file would just get pulled, like every other
Hey Unirgy,
Seeing how this was quite some time ago, I'm not expecting a response, but
I would very much appreciate knowing if you ever figured what was causing
the template load error for you? We are experiencing it sporadically but it
has been difficult to reproduce. Thanks!
On Saturday,
