Skip to content

Don't persist or send cookies to Replicate API #102

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

Merged
merged 1 commit into from
May 19, 2023
Merged

Conversation

nickstenning
Copy link
Contributor

Replicate's API does not use cookies and even if we return cookies the client should not save and replay them.

@nickstenning nickstenning force-pushed the forget-all-cookies branch 2 times, most recently from 23d911c to 718006a Compare May 11, 2023 15:18
Replicate's API does not use cookies and even if we return cookies the
client should not save and replay them.

Co-authored-by: Mattt Zmuda <mattt@replicate.com>
Signed-off-by: Nick Stenning <nick@whiteink.com>
Signed-off-by: Mattt Zmuda <mattt@replicate.com>
@mattt mattt force-pushed the forget-all-cookies branch from 3d0f547 to df0637a Compare May 19, 2023 22:41
Copy link
Contributor

@mattt mattt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nickstenning Thanks so much for contributing this. The implementation details for a requests session that doesn't persist cookies is trivial, so I decided to inline this functionality with a new, equivalent class instead of adding a new dependency.

@mattt mattt merged commit 9929170 into main May 19, 2023
@mattt mattt deleted the forget-all-cookies branch May 19, 2023 22:43
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