If this was an existing app prior to 1.5.0 then it is not fixed yet, 1.5.0 put the fix in but we still need to clean up apps that were created prior to 1.5.0.
Hope that helps, Greg On Wed, May 11, 2011 at 10:54 AM, Stephen Johnson <onepagewo...@gmail.com>wrote: > I'm confused. I have an HR app and this is what I see when I look at the > headers using Firebug for one of my images. You're saying this should be > different? > On Wed, May 11, 2011 at 9:36 AM, Francois Masurel <f.masu...@gmail.com>wrote: > >> What is rather strange is that cache headers work perfectly fine with MS >> applications. >> >> I hope it's not a way to increase billing ;-) >> >> I'm personaly concerned as I'm serving most of my image and file contents >> dynamically from datastore or memcache. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
