Internal error when setting include_entities=1

pjamourik
@pjamourik Peter van Mourik

Hi Guys,

I'm getting an 500 error (error code 131) when I query the Twitter Search API for a specific keyword (ziekteverzuim) and setting include_entities=1. When I disable include_entities all works fine.

This works
http://search.twitter.com/search.json?q=ziekteverzuim&lang=nl&rpp=100&result_type=recent&include_entities=0

And this doesn't
http://search.twitter.com/search.json?q=ziekteverzuim&lang=nl&rpp=100&result_type=recent&include_entities=1

This seems a bit odd to me, I hope someone can help!

Any help is appreciated.

Kind regards,

Peter

1 day 11 hours ago

Replies

episod
@episod Taylor Singletary

This is strange -- I'll file a bug with the search team. What's stranger is if you take the lowest ID and highest ID from the successful result, transpose them to since_id and max_id values and do the same query with entities enabled, there's no problem with the request. http://search.twitter.com/search.json?max_id=232493104798777500&q=ziekteverzuim&lang=nl&result_type=recent&since_id=229629176179724250&include_entities=true

1 day 4 hours ago
pjamourik
@pjamourik Peter van Mourik

Thanks Taylor, That indeed makes this whole issue even weirder, hope all will be fixed soon :)

10 hours 40 min ago