Use standard Netscape cookies.txt format for loading/saving cookies #287
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes cookies are needed to get past the "Too many users have viewed or downloaded this file recently" error. Currently the cookies format used is a non-standard JSON list of key value pairs. It would be easier for users (e.g. #271) if the cookies format was something standard, like cookies.txt, as there are many browser extensions for downloading cookies.txt files for a website. This PR makes saving/loading cookies in Netscape format the default, but allows the program to load the old style JSON format if no cookies.txt is present.