When I make two searches using different locations and then re-request the first search, I get results for the second location.
Example:
1st Request: (Chicago)
https://search.twitter.com/search.json?rpp=40&result_type=recent&geocode=41.8781136,-87.6297982,25mi&q=tacos
2nd Request (California):
https://search.twitter.com/search.json?rpp=40&result_type=recent&geocode=36.778261%2C-119.4179324,25mi&q=tacos
3rd Request (Chicago again - returns results for California):
https://search.twitter.com/search.json?rpp=40&result_type=recent&geocode=41.8781136,-87.6297982,25mi&q=tacos
After waiting a minute or two, re-requesting URL #3 returns the correct results.
Updates
- Thanks for this detailed report; I've sent this to the search team for investigation.
- 2012-05-17 We believe to have fixed the remaining factors causing these erratically cached geo-based responses. Please open a discussion thread if you're still experiencing this bug with the Search API. Thanks!