Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2706)

Issue 154105: don't delete oauth tokens on 403 responses

Can't Edit
Can't Publish+Mail
Start Review
Created:
14 years, 5 months ago by beaton
Modified:
14 years, 5 months ago
Reviewers:
Paul Lindner, shindig.remailer, etnu
Base URL:
https://svn.apache.org/repos/asf/incubator/shindig/trunk/
Visibility:
Public.

Patch Set 1 #

Total comments: 2

Messages

Total messages: 3
beaton
So it turns out that Twitter returns 403 responses when a client is rate limited. ...
14 years, 5 months ago (2009-11-13 01:58:44 UTC) #1
etnu
This seems reasonable. I assume you've tested enough service providers to be confident that none ...
14 years, 5 months ago (2009-11-13 02:09:50 UTC) #2
beaton
14 years, 5 months ago (2009-11-13 17:08:07 UTC) #3
Yep, tested against several service providers.  None return 403 for
unauthorized.

They all return 401 for multiple reasons, unfortunately.  So there are still
some cases where we will delete a token that might not actually have been
revoked.  For example, most service providers can't distinguish between a token
that has been revoked and a bad signature due to bug on our side.

This is still better off than we were before.

I made the switch to using constants in those places.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b