On Sat, Mar 19, 2011 at 8:32 PM, Brandon Wirtz <drak...@digerat.com> wrote: > > 1. Caching doesn’t work, and because of the way headers are > forced to be set all requests expire immediately so the user won’t cache > either. > > (Headers from a request) > > HTTP/1.1 405 Method Not Allowed > Content-Type: text/html; charset=utf-8 > Cache-Control: no-cache, must-revalidate > Expires: Fri, 01 Jan 1990 00:00:00 GMT > Set-Cookie: S=apphosting=5hoCHm4x9c3ZrrxQEN5Q4A; path=/ > Date: Sat, 19 Mar 2011 19:37:21 GMT > Pragma: no-cache > Server: Google Frontend > Content-Length: 0
These look like headers from a response, not a request, and the response code is 405: Method Not Allowed. ie. the request was something other than a GET, POST, PUT or DELETE, in which case you might expect the error response to force a no-cache header. Are you sure your test is accurate? -- 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.
