I am a developer on a fairly mature product that has been using the Java based Signpost OAuth library successfully for many months. (signpost 220.127.116.11).
We recently moved from cloud servers to our own in-house servers (which of course changed our requesting IP, although the domain name was unchanged), and our login/oauth process has become agonizingly slow. Specifically, I’ve determined through careful log statements that these two Signpost calls seem to take a very long time, sometimes 30-45 seconds:
authUrl = provider.retrieveRequestToken(consumer, callback);
Does anyone know of an explanation for this, given that nothing else in the system has changed? Is it possible that Twitter is somehow caching IPs or throttling requests based on IP? Would it make sense to recreate the app key/secret?
We are really at a loss to understand the sudden (and dramatic) change in response time. Any thoughts or suggestions very much appreciated.