I'm seeing a bug where some OpenSocial JS proxy requests are cached in my browser (IE, FF, and Safari).

Upon inspecting these requests, I noticed that most of the time the "ts" (timestamp) parameter are not included, so naturally the browser caches the request.

By the way, the app I'm having problems with is 102843, My Top Artists.

Here are some pages that exhibit the caching problem:

• http://www.myspace.com/johntantalo
• http://www.myspace.com/sdultimate
  

Hi John,

That's the correct behaviour.  For 0.7 apps we don't append a timestamp, it's up to the developer to determine whether they want the browser to cache the request or not.  You might be confusing this with API calls, for which we do append a timestamp.

We incorrectly started appending a timestamp parameter for 0.8 makeRequest calls, but this can be removed via:

Thanks, Chad. Ideally, the browser cache should key off of the opensocial_owner_id (in my case at least). Would it be better to wait until after the "get owner" API call returns and include the owner id in the makeRequest URL or add a timestamp to every makeRequest call? The difference seems negligible.

 Hey John, really up to you.  The more that you can cache the better for both us and you though!