jordan-wright
Status 403
How are people dealing with status 403 and the throttle limits?
I did a loop to create random email, fetch a session and then do a call... still getting a 403.
Any work arounds?
I've randomised the auth email every now and again, and changed the IP address periodically - that combination is working well for me.
So the email you're using is an authenticated email and not a random generated?
Cause when I just did randomly generated, worked for a bit then got locked down giving me 403: unauth_throttle_limit
There is a difference between an authenticated and non authenticated user.
Using my personal email and making a call to login_status, it showed me as unauthenticated but still gave me a session token... Which sometimes works. When I make a call and copied and pasted the cookies from my browser, it retuned I am authenticated with google and LinkedIn, the session token never fails then.
On Wednesday, June 11, 2014, mrbirl [email protected] wrote:
I've randomised the auth email every now and again, and changed the IP address periodically - that combination is working well for me.
— Reply to this email directly or view it on GitHub https://github.com/jordan-wright/rapportive/issues/11#issuecomment-45716043 .
Mohamed El Mahallawy
@mmahalwy4167101981
No it's random generated, by auth I meant the one I used to get the session token - probably bad choice of words! I'm just using random emails - I use one until it fails, then generate another and use that etc.
To my knowledge, this error code is received after sending too many requests using the same IP address. Switching the email address doesn't help, so the only known solution is to either throttle your requests, or periodically switch IP addresses.
I have had the problem with same emails when on production then on development which would have different IP addresses...
On Wed, Jun 11, 2014 at 4:02 PM, Jordan Wright [email protected] wrote:
To my knowledge, this error code is received after sending too many requests using the same IP address. Switching the email address doesn't help, so the only known solution is to either throttle your requests, or periodically switch IP addresses.
— Reply to this email directly or view it on GitHub https://github.com/jordan-wright/rapportive/issues/11#issuecomment-45791973 .
Mohamed El Mahallawy
@mmahalwy4167101981
I have it on one IP address first and one email, then it'll fail and switch emails - switching emails works for a while, then it'll switch IP in addition. So Swapping emails works for a while, and then you'll need to switch IP's. I've been doing that, and never fails now.
May be able to this weekend. It's in Ruby
On Friday, June 13, 2014, Rbucks [email protected] wrote:
Anyone willing to fork and post on here with the IP and email auth?
— Reply to this email directly or view it on GitHub https://github.com/jordan-wright/rapportive/issues/11#issuecomment-45976616 .
Mohamed El Mahallawy
@mmahalwy4167101981
If anyone forks this and gets it working, please don't hesitate to send a PR - I'll happily merge!