-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Response:{u'reason': 110, u't': u'refresh', u'seq': 0} #25
Comments
Same problem here, Ubuntu 14.04 LTS with python 2.7.6. |
i've hit the same snag on windows 10, python 2.7.10. i've been trying cookies from different pull requests and that might be part of the issue. not every pull request in the network tab has a full response object. some of them are just heartbeats and some don't have any data at all. i changed cookies until i stopped getting 403s, and made sure to grab a cookie from a pull request that had a full response, but now i get a 200 with the same issue:
a couple of things look off to me. there's the unicode prefixes when printing to the console, while the facebook reponse has an
and there's the seq number always being zero. i don't think it's exactly a nonce, but if you watch your own facebook network requests it does seem to increment periodically. edit to add, that's the facebook response that's always 0, not the request we're sending. changing the request's sequence number doesn't seem to fix the issue |
I think you need a new cookie. I had this issue and it was solved after I grabbed a new cookie. |
Getting a new cookie to secrets.txt made it work to me |
So when I run
python fetcher.py
I just repeatedly get this line in the console:Response:{u'reason': 110, u't': u'refresh', u'seq': 0}
Can anyone shed any light on what it is and how to fix it? Nothing is going into the log directory at all.
If I fiddle around with the
SECRETS.txt
file and make something invalid it fails for different reasons, so I can only assume the cookie and IDs are working ok.This is on Windows 7 if that makes a difference...
The text was updated successfully, but these errors were encountered: