Skip to content
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

Cookie Management does not work while running whole folder/collection #2682

Open
2 tasks done
mosotu88 opened this issue Jul 22, 2024 · 1 comment
Open
2 tasks done
Labels
bug Something isn't working

Comments

@mosotu88
Copy link

I have checked the following:

  • I use the newest version of bruno.
  • I've searched existing issues and found nothing related to my issue.

Describe the bug

If I run all requests of a folder, the cookie management does not work same as when I run the requests one by one

Steps to reproduce with a simple example:

  1. Delete all cookies in bottom left cookie menu.
  2. Add two requests to a folder. Example: GET https://github.com
  3. Run folder

Expected:
Cookies are provided in request headers when running folders
Example:
First response will set cookie (in example: response header includes "< set-cookie: _gh_sess=..." )
Second response will not set a cookie as it should already be provided

Actual.
Cookies are not provided when running folders
Example:
First response of GET https://github.com sets session cookie (in example: response header includes "< set-cookie: _gh_sess=..." )
Second response of GET https://github.com also sets session cookie, eventhough it was already set before (in example: response header includes "< set-cookie: _gh_sess=..." )

If I run the requests one by one instead of running the folder, the cookie management works as expected.

.bru file to reproduce the bug

Attached example collection with example requests and a test in the second
Cookie Folder Run Test.zip

Screenshots/Live demo link

see provided bruno collection in attachments to reproduce the bug.

@mosotu88 mosotu88 added the bug Something isn't working label Jul 22, 2024
@sanjai0py
Copy link
Collaborator

Hey @mosotu88, thank you for taking the time to report this issue. It looks like there may be a bug. I will investigate and get back to you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants