You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Might be the same as #38, not sure if NYT has put in place some mitigation measures or not.
Invoked with xword-dl -u <myuser> -p <mypass> nyt
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://myaccount.nytimes.com/svc/ios/v2/login
I was able to authenticate from one location (home), but not from another (office). Manually copying an NYT-S cookie from an already authenticated session and dropping it into the yaml file for the office worked.
Any ideas on what to try?
The text was updated successfully, but these errors were encountered:
Hm, I am also seeing this error at least intermittently. I think it does reflect some kind of mitigation measures. (I have futzed around a bit with values that I'm pulling directly off mitmproxy from my own app instance, but haven't been able to circumvent it.)
I have to think a bit on how to best solve this. If it is like #38, then maybe it'll just resolve itself, though I kind of doubt it. My hunch is that either we should treat authentication as out-of-scope and provide documentation for manually copying over the NYT-S token or similar, OR switch to a less brittle method. I'm open to suggestions on that front!
Might be the same as #38, not sure if NYT has put in place some mitigation measures or not.
Invoked with
xword-dl -u <myuser> -p <mypass> nyt
I was able to authenticate from one location (home), but not from another (office). Manually copying an NYT-S cookie from an already authenticated session and dropping it into the yaml file for the office worked.
Any ideas on what to try?
The text was updated successfully, but these errors were encountered: