There seems to be a problem with the search API and caching. If the only change between calls is in the meta (m) parameter, I get the same result as the previous call - for instance:
These two calls will produce exactly the same results - and I can change the m parameter value to anything (even invalid combinations) and still see the same result. A change in any of the other parameters will give a different result.
I found that I can work around the issue by adding a "dummy" parameter with a different value on each request - but this is at best a band-aid (and an unreliable one, should you decide to give an error on any request with invalid parameters in the future)
I have confirmed through network analyzer and by using different clients in different networks that this is not a client issue - the caching is happening on your side.
There seems to be a problem with the search API and caching. If the only change between calls is in the meta (m) parameter, I get the same result as the previous call - for instance:
http://api.amp.active.com/search?m=meta:channel=Swimming&v=xml&f=activities&s=date_asc&num=30&page=1&api_key=wuhmn9ye94xn3xnteudxsavw http://api.amp.active.com/search?m=meta:channel=Triathlon&v=xml&f=activities&s=date_asc&num=30&page=1&api_key=wuhmn9ye94xn3xnteudxsavw
These two calls will produce exactly the same results - and I can change the m parameter value to anything (even invalid combinations) and still see the same result. A change in any of the other parameters will give a different result.
I found that I can work around the issue by adding a "dummy" parameter with a different value on each request - but this is at best a band-aid (and an unreliable one, should you decide to give an error on any request with invalid parameters in the future)
I have confirmed through network analyzer and by using different clients in different networks that this is not a client issue - the caching is happening on your side.
Message edited by Kjetil Samuelsen 13 years ago
Tags
active Admin – 13 years ago
Apologies for the late response. I've got engineering looking into this. Stay tuned.
active Admin – 13 years ago
We've found the bug and our engineers are creating the patch. We'll be putting the patch in place on Tuesday night at 11pm PST.