thanks for the comprehensive debugging, Dave and David! it definitely
sounds like new header munging on app engine's part may be the problem.
Dave, your idea of sending the API calls to a different endpoint and
examining the headers sounds like a great lead. i'm looking forward to the
results!
as another data point, there may be more to it than just punctuation
characters. i see the error with pretty much any tweet content and
username. i reproduced it just now by attempting to tweet "foo" (just those
three characters) as @schnarfed. sigh.
On Wednesday, April 29, 2015 at 9:58:38 AM UTC-7, Dave Loomer wrote:
>
> (what I was getting it with the previous post is: if any of you need this
> for your day jobs, you are welcome to try the same yourselves in the
> meantime ;) )
>
> On Wednesday, April 29, 2015 at 11:56:52 AM UTC-5, Dave Loomer wrote:
>>
>> All: I won't have time to do this in the next several hours (my app
>> engine app is not my day job), but I think tonight I'll try changing the
>> api.twitter.com endpoint to point to a URL I own, and then examine the
>> URLs / query strings and headers received from my prod vs. dev code to see
>> if the encoding is any different.
>>
>> I figure that could help point to whether it's a urlfetch issue. Only
>> other thing I can think of, if it's not urlfetch, is that the oauth
>> signatures are being generated differently in prod vs. dev, due to a
>> difference in some built-in python library on the prod server, and that
>> will be much more difficult to debug since the timestamp and nonce prevent
>> you from comparing dev vs prod requests character-by-character.
>>
>>
>> On Wednesday, April 29, 2015 at 9:36:17 AM UTC-5, Ryan Barrett wrote:
>>>
>>> hi all! a number of us have started seeing twitter API errors in prod
>>> GAE in the last week or so. write calls and some search calls are returning
>>> HTTP 401 {"errors":[{"code":32,"message":"Could not authenticate
>>> you."}]} for all users with no code changes on our end. the
>>> particularly odd part is that the same calls with the same code, twitter
>>> app key/secret, and even *the exact same user access token key/secret*
>>> work fine in dev_appserver.
>>>
>>> we're on python and mostly using tweepy. our current theory is that
>>> twitter has blacklisted or graylisted app engine's external facing IPs. can
>>> you think of any other ideas?
>>>
>>> more details in this twitter dev forum post.
>>> <https://twittercommunity.com/t/post-to-statuses-update-json-started-hitting-error-32-could-not-authenticate-you-with-no-code-changes/36495>
>>>
>>> thanks in advance!
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/75642a3b-ec93-4a89-a549-2fd9280bf410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
