Hey Twitter API devs, We're working on daemons to poll the search API, and we want to make sure that our code will behave correctly when it encounters a RETRY_AFTER header. We think our code should work correctly, but we'd like to be able to test it with a real RETRY_AFTER header. Could you add the option for us to add a RETRY_AFTER=X parameter to the HTTP request that will force your servers to return a RETRY_AFTER header of X seconds, so that we can easily test our code and then remove it?
Thanks.
