| Issue 742: | Search with since_id returns 403 with used with some options (including: filter:links, geocode) | |
| 7 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
What's the problem you're seeing? Search API since_id request no longer works with filter:links I query with a url like http://search.twitter.com/search.atom?q=video%20filter:links&rpp=100&since_id=2309008249 once every 15 second, with the last id I get from the last call. This query stopped working sometime on 2009-06-23. Please note that querying without filter:links works http://search.twitter.com/search.atom?q=video&rpp=100&since_id=2309008249 What was the request you made (if applicable)? Be sure to obscure your Basic Auth headers. http://search.twitter.com/search.atom?q=video%20filter:links&rpp=100&since_id=2309008249 What was the full HTTP response, with headers (if applicable) http://search.twitter.com/search.atom?q=video%20filter:links&rpp=100&since_id=2309008249 GET /search.atom?q=video%20filter:links&rpp=100&since_id=2309008249 HTTP/1.1 Host: search.twitter.com User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060309 Ubuntu/8.04 (hardy) Firefox/3.0.11 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive HTTP/1.x 403 Forbidden Date: Wed, 24 Jun 2009 12:03:04 GMT Server: hi Status: 403 Forbidden X-Served-From: b004 Cache-Control: max-age=60, must-revalidate, max-age=1800 Content-Type: application/xml; charset=utf-8 X-Served-By: c004.twitter.com Expires: Wed, 24 Jun 2009 12:33:04 GMT Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 111 X-Varnish: 271475175 Age: 0 Via: 1.1 varnish X-Cache-Svr: c004.twitter.com X-Cache: MISS Connection: close |
||||||||||||
,
Jun 24, 2009
Please note that the id passed to since_id is 15 seconds old. So, the error message "since date or since_id is too old" does not apply, and i'm well under the rate limits. |
|||||||||||||
,
Jun 24, 2009
I'll look into it.
Status: Accepted
Owner: m...@twitter.com Labels: -Priority-Medium Priority-High Component-Search |
|||||||||||||
,
Jun 24, 2009
I believe I have found the root cause of this. A fix is waiting to be reviewed. |
|||||||||||||
,
Jun 24, 2009
I have a similar error: I get a 403 forbidden if I request the url: http://search.twitter.com/search.json?rpp=100&geocode=37.0902400%2C-95.7128910%2C1500km&q=HTC+OR+iran&since_id=2310721428 this will work: http://search.twitter.com/search.json?rpp=100&geocode=37.0902400%2C-95.7128910%2C1500km&q=HTC+OR+iran&since_id=0 this works too: http://search.twitter.com/search.json?rpp=100&q=HTC+OR+iran&since_id=2310721428 Maybe it's the same problem? |
|||||||||||||
,
Jun 24, 2009
I am finding that since_id not working even with normal results. Eg http://search.twitter.com/search.atom?geocode=44.977482%2C-93.264351%2C10km&rpp=100&since_id=2312886922&page=1 - there really should be only 30-50 results from that since_id (at least when I am posting this), but it is complaining that the since_id is too old. |
|||||||||||||
,
Jun 24, 2009
The fix awaiting review fixes a 403 issue with some search operators, like filter:links and geocode searches. |
|||||||||||||
,
Jun 24, 2009
Issue 745 has been merged into this issue. |
|||||||||||||
,
Jun 24, 2009
(No comment was entered for this change.)
Summary: Search with since_id return 403 with used with some options (filter:links, geocode)
|
|||||||||||||
,
Jun 24, 2009
(No comment was entered for this change.)
Summary: Search with since_id returns 403 with used with some options (including: filter:links, geocode)
|
|||||||||||||
,
Jun 24, 2009
Fix deployed. Verified with: curl 'http://search.twitter.com/search.atom?q=video%20filter:links&rpp=100&since_id=2309008249' curl 'http://search.twitter.com/search.json?rpp=100&geocode=37.0902400%2C- 95.7128910%2C1500km&q=HTC+OR+iran&since_id=2310721428' curl 'http://search.twitter.com/search.atom?geocode=44.977482%2C- 93.264351%2C10km&rpp=100&since_id=2312886922&page=1'
Status: Fixed
|
|||||||||||||
,
Jun 24, 2009
Thanks a lot. That was quick. |
|||||||||||||
,
Sep 09, 2009
Now breaks searches that are ONLY geocode && since_id (e.g. no keywords). We're doing this for location-sensitive tweets. |
|||||||||||||
,
Nov 05, 2009
Found a very similar issue: Sending a search quest has my geocode ignored, a since_id added, and apparently an out-dated since_id. My URL: http://search.twitter.com/search.json?q=Burger+King&geocode=37.7746%2C- 122.51%2C1km&rpp=30 My returned JSON results: {"results":[],"max_id":5454105412,"since_id":5264894286,"refresh_url":"? since_id=5454105412&q=Burger+King","results_per_page":30,"page":1,"completed_in":0.064994,"warning":"a djusted since_id to 5264894286 (2009-10-29 18:00:00 UTC), requested since_id was older than allowed","query":"Burger+King"} Later, adding the minimum since_id the errors indicates (5264894286) in addition to q, geocode, and rpp, I receive the same error (in other words, the error tells me to use a since_id that happens to be the exact since_id I used). Additionally, using a since_id that falls between the minimum (5264894286) and the max (5454105412) returns no connection at all. |
|||||||||||||
 Sign in to add a comment
|
|||||||||||||
