I believe GAE caches URL requests for a period, so that would jive with what you're seeing.
However apparently you can set the cache-control header in your request to force no caching on your request. It's discussed here: http://groups.google.com/group/google-appengine/browse_thread/thread/ae52ac9100d8f18c/87c32daa06eb5df1?lnk=gst&q=urlfetch+caching#87c32daa06eb5df1 The user there however reported that they couldn't get it to work...maybe the header was being set incorrectly or something, but it might be worth you checking it out for yourself. On Feb 17, 9:05 am, Adam Johnson <[email protected]> wrote: > It appears that GAE has done some tricks recently to boost urlfetch > scalability. My app has steadily increasing traffic, but getting less > 'simultaneous dynamic request limit' problem. > > However, some urlfetch behaviors become really weird now. The urlfetch will > return some results that you know for sure deleted from the url you are > fetching for. > > This can be easily tested out. According to my experience, very frequently > happening against a YahooGroup RSS feed URL. > > I go to my YahooGroup and delete a msg. Then I try that YahooGroup RSS URL > in my browser, it shows clearly that msg entry disappeared. Then I use GAE > to fetch the URL, GAE returns me an xml with the delete msg entry inside. > > Adam -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
