- Notifications
You must be signed in to change notification settings - Fork51
fix: 403 failed issue#66
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
fix: added some request headers and make it always.
leozhao21 commentedMar 18, 2024
I tried it, when submit action is error |
dngurdl commentedMar 23, 2024
I'll add that the proposed solution by@woung717 only worksafter a user has successfully logged in (have the csrftoken cookie as well as the SESSION_ID cookie set). The no-browser in the middle approach has completely died out imo. A no-browser-cookie login is a valuable way to use leetcode-cli and there seems to have been a recent leetcode backend update that disables the no-browser-cookie approach. Use-case that fails is 3rd party login (via Github for instance) without using cookies from a browser. I can confirm that 3rd party login w/o a browser cookie worked up untill Jan 2024 (and for the past 3 years). Now, the 3rd party login (Github in my case) fails with a 403 due to a cloudflare challenge issue. |
No description provided.