in other words, is there a way to get more information as to why? bad header, bad format, missing parm etc?
posting to the API call with Java HttpURLConnection - https://api.twitter.com/1.1/statuses/update.json
authorisation header looks correct, certainly seems awfully similar to the samples that can be generated on the API page for that call
authorizationHeader:
OAuth
oauth_consumer_key=“EFMJBGCCRwr85EiGwa3KzA”,
oauth_nonce=“CXOHIVALYSPHJUJSJVDAQDYAMNTDXJYD”,
oauth_signature=“O775r7iQLP9tmOsvN1SqyyjdlI8%3D%0A”,
oauth_signature_method=“HMAC-SHA1”,
oauth_timestamp=“1363288401”,
oauth_token=“1148882486-JwyF1HXsKCELLP4AthvSB85puhcvWwATJikrNGk”,
oauth_version=“1.0”
is there a dev link that I can post my query to that supplies more information rather than the mainstream active APIs?
episod
#2
Auth errors tend to be vague so as not to leak any unnecessary information.
In most cases, an OAuth 1.0A error occurs because of something invalid about the signature base string – or a disagreement between the POST or query string you’re sending and what that signature base string describes. First make sure that your request is completely valid HTTP 1.1, with all the escaping of bodies and URLs that that requires. Then make sure that when your code is generating signature base strings, its consideration of how escaping is approached is based on the already valid HTTP 1.1 you’re performing.
