Skip to content

Conversation

@patricker
Copy link
Contributor

Right now the api object re-runs Auth on every run. This adds an option to export your cookies to a JSON file and import them instead of re-doing an auth.

I believe this will also create a path for working around the Captcha error when running the script in the cloud.

  • Auth from your local dev box. Export the cookies to a JSON file by calling export_cookies.
  • In your cloud environment, use the exported cookies file for auth, skipping the entire captcha flow.

(I'm fine with re-basing as needed after my other PR gets merged)

@ma2za
Copy link
Owner

ma2za commented Dec 6, 2023

great workaround... i wonder if there is any expiration

@ma2za ma2za mentioned this pull request Dec 6, 2023
@ma2za
Copy link
Owner

ma2za commented Dec 6, 2023

can you fix the merge conflicts??

@patricker
Copy link
Contributor Author

@ma2za conflicts resolved.

@patricker
Copy link
Contributor Author

great workaround... i wonder if there is any expiration

Also, I expect there is an expiration. Often times though if you are using the cookie it will get extended. So it would be advisable to re-export your cookies after each session and overwrite your old copy.

@ma2za ma2za merged commit e0743f9 into ma2za:main Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants