When paging through direct messages using OAuth, every now and then
one gets a 401 HTTP response without an accompanying error message
from Twitter, meaning, there is no error construct that would usually
say, "Could not authenticate you," or "Invalid/used nonce". Just
nothing.

This happens in a completely unpredictable manner. You sometimes get
it on page=1, sometimes on page=4, etc. And with the very next attempt
of the exact same call, you get the list and a 200 OK.

Has anyone else experienced the same?

Reply via email to