[twitter-dev] 503 with gigantic retry-after value

[Benjamin Darfler]

We are using the search api and respecting the 503 and retry-after
values however I've seen a retry value in the 40 YEARS range a few
times in the past week. Whats up with that?

Ben