-
Notifications
You must be signed in to change notification settings - Fork 51
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
requests.exceptions.HTTPError: 403 Client Error #104
Comments
it looks like the API now need an additional "X-CSRF-Token" header or it will response 403. |
Agree. Same issue is received with multiple session IDs/cookies/posts. |
Is there a way to solve this? |
From what I can tell this is only required on API calls to the /posts endpoint currently. A new CSRF token will be generated on each page load, as seen in the post page source:
This token is present on every page but I don't see any other places it's actively being used. We will probably want to eventually implement this for every API request by first hitting the actual page everywhere, but I believe what needs to happen for now is:
|
Potential closure to #104 pending full checks
The referenced commit should fix this. Would appreciate tests to see if there are any other requests that seem to return 403. |
It's seems to be working to me. |
Got enough reports this is working so closing out, new release soon. |
Today I got this message.
Checked my cookies.txt, updated to latest one but no luck.
The text was updated successfully, but these errors were encountered: