Skip to content

Commit 10d10a3

Browse files
committed
heroku link
1 parent 4605da5 commit 10d10a3

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

README.md

+6
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,12 @@
44

55
Once configured with a key and secret to a registered twitter app, `twitterproxy` uses OAuth to sign in users with their twitter account. Once signed in, it can proxy requests to the twitter API on behalf of the signed in user.
66

7+
A test instance is deployed on heroku:
8+
9+
[http://twitterproxyapp.herokuapp.com/](http://twitterproxyapp.herokuapp.com/)
10+
11+
> Note that this is a free instance which means that the first request could trigger deployment and the page may take a few seconds to load.
12+
713
Signing in results in an access token and secret for the user. This is encoded and set in a cookie which is then used when invoking the twitter API. This cookie is set on the root domain which means any app on that domain can use the proxy.
814

915
> Note that if you use the project as-is, the cookie will not be encrypted. Encoding the token and secret in plaintext is not recommended. Developers are encouraged to provide a strong implementation of the ``twitterproxy.Crypto`` interface to support encryption / decryption. Alternatively, the token and secret can be persisted on the server.

0 commit comments

Comments
 (0)