Thanks Thomas. This helped us find the ultimate root of the problem. We had mapped a servlet (quite by accident) to a URL pattern that matched our module name. So after deploying a new version, requests to the old .cache.js files were being picked up by this servlet rather than throwing a 404 error and generating an onFailure.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/i4u_s0Y6e88J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.