[GH-ISSUE #3532] [bug]: set-cookie in response headers not working

kerem commented

2026-03-16 19:11:33 +03:00

Owner

Originally created by @xshadowlegendx on GitHub (Nov 10, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3532

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I use hoppscotch cloud with proxy interceptor to call to my backend server and for login endpoint, the server return refresh and fingerprint httponly cookies and after successful login hoppscotch only shows 1 set cookie response, the issue is same as this one and also subsequent request did not send the cookie as well, I tried testing this with postman from the web, and did not configure anything I can call login endpoint and the response show both cookies and also subsequent request will also send those cookies along

Steps to reproduce

you can try this endpoint of my test server on both hoppscotch and postman, postman will just works while hoppscotch did not correctly fold those multiple cookies and did not send them with subsequent request as well

POST https://identity.lsa.xdevx.dedyn.io/authn/password/login

user_id = 7131aa28-ca21-4ff7-8273-5e16ab304e25
password = 13db2588XyZ

content-type = application/x-www-form-urlencoded

Environment

Production

Version

Cloud

Originally created by @xshadowlegendx on GitHub (Nov 10, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3532 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I use hoppscotch cloud with proxy interceptor to call to my backend server and for login endpoint, the server return refresh and fingerprint httponly cookies and after successful login hoppscotch only shows 1 set cookie response, the issue is same as [this one](https://github.com/hoppscotch/hoppscotch/issues/1546) and also subsequent request did not send the cookie as well, I tried testing this with postman from the web, and did not configure anything I can call login endpoint and the response show both cookies and also subsequent request will also send those cookies along ### Steps to reproduce you can try this endpoint of my test server on both hoppscotch and postman, postman will just works while hoppscotch did not correctly fold those multiple cookies and did not send them with subsequent request as well ``` POST https://identity.lsa.xdevx.dedyn.io/authn/password/login user_id = 7131aa28-ca21-4ff7-8273-5e16ab304e25 password = 13db2588XyZ content-type = application/x-www-form-urlencoded ``` ### Environment Production ### Version Cloud

kerem added the

bug

need testing

desktop

labels

2026-03-16 19:11:33 +03:00

kerem commented

2026-03-16 19:11:45 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 10, 2023):

Cookie capturing is not available in the Hoppscotch web app.

Download Hoppscotch Desktop App to manage Cookies.

@liyasthomas commented on GitHub (Nov 10, 2023): Cookie capturing is not available in the Hoppscotch web app. [Download Hoppscotch Desktop App](https://hoppscotch.com/download) to manage Cookies.

kerem commented

2026-03-16 19:11:50 +03:00

Author

Owner

@xshadowlegendx commented on GitHub (Nov 10, 2023):

hello @liyasthomas I also tried the desktop app one also same behavior

@xshadowlegendx commented on GitHub (Nov 10, 2023): hello @liyasthomas I also tried the desktop app one also same behavior

kerem commented

2026-03-16 19:11:55 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 10, 2023):

Sorry for the inconvenience, as of today, you've to manually add the cookie string to the domain. You can follow the instructions in the cookies documentation to manually add cookies.

The ability to auto magically set-cookies from response headers is coming soon in Hoppscotch Desktop App. Thank you for your patience. Keeping this issue ticket open to track feature progress.

@liyasthomas commented on GitHub (Nov 10, 2023): Sorry for the inconvenience, as of today, you've to manually add the cookie string to the domain. You can follow the instructions in the [cookies documentation](https://docs.hoppscotch.io/documentation/features/cookies) to manually add cookies. The ability to auto magically set-cookies from response headers is coming soon in Hoppscotch Desktop App. Thank you for your patience. Keeping this issue ticket open to track feature progress.

kerem commented

2026-03-16 19:12:00 +03:00

Author

Owner

@felipebontempo commented on GitHub (Mar 7, 2024):

Sorry for the inconvenience, but maybe my problem is exactly this:

Below are two images, one is how Postman returns and how hoppscotch returns.

The problem is that hoppscotch is missing a "Set-cookie", there should be two, and they are exactly the same call in both tools.

What will be the problem?

I'm sending it here precisely because I think it's a problem with the tool, correct me if I'm wrong.

@felipebontempo commented on GitHub (Mar 7, 2024): Sorry for the inconvenience, but maybe my problem is exactly this: Below are two images, one is how Postman returns and how hoppscotch returns. The problem is that hoppscotch is missing a "Set-cookie", there should be two, and they are exactly the same call in both tools. What will be the problem? I'm sending it here precisely because I think it's a problem with the tool, correct me if I'm wrong. ![CleanShot 2024-03-07 at 10 18 42@2x](https://github.com/hoppscotch/hoppscotch/assets/26803292/ee1504f7-b14d-45d1-b410-cf087a36594b) ![CleanShot 2024-03-07 at 10 19 22@2x](https://github.com/hoppscotch/hoppscotch/assets/26803292/451587ef-ebb7-49d3-8afd-786edf8322b7)

kerem commented

2026-03-16 19:12:05 +03:00

Author

Owner

@felipebontempo commented on GitHub (Mar 8, 2024):

I just tested it on the Bruno API, both values come in the "set-cookie" variable, I believe there is a data cut in Hoppscoth

@felipebontempo commented on GitHub (Mar 8, 2024): I just tested it on the Bruno API, both values come in the "set-cookie" variable, I believe there is a data cut in Hoppscoth

kerem commented

2026-03-16 19:12:10 +03:00

Author

Owner

@DarkDonnerGunther commented on GitHub (Aug 22, 2024):

Is here any update? I need to save cookies automatically to use them as request.

@DarkDonnerGunther commented on GitHub (Aug 22, 2024): Is here any update? I need to save cookies automatically to use them as request.

kerem commented

2026-03-16 19:12:15 +03:00

Author

Owner

@CIenthusiast commented on GitHub (Aug 27, 2024):

How is this not fixed already. This is a must-have basic for any api tool.
I get that you could technically disable security for your local development or you could just copy it manually to your cookie-store. Who tf does that?

@CIenthusiast commented on GitHub (Aug 27, 2024): How is this not fixed already. This is a must-have basic for any api tool. I get that you could technically disable security for your local development or you could just copy it manually to your cookie-store. Who tf does that?

kerem commented

2026-03-16 19:12:20 +03:00

Author

Owner

@Paper-Folding commented on GitHub (Aug 27, 2024):

I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using hoppscotch's "test" tab, and use env value in cookie header with accessToken=<<accessToken>>;refreshToken=<<refreshToken>> (I'm using jwt authentication).
My simple test script to do that:

const tokens = pw.response.headers
  .filter((ele) => ele.key === "Set-Cookie")
  .map((ele) => ele.value.split(";")[0].split("="));
pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]);
pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1])

The shortcoming is, you have to add this cookie header for each subsequent authentication required requests.

@Paper-Folding commented on GitHub (Aug 27, 2024): I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using hoppscotch's "test" tab, and use env value in cookie header with `accessToken=<<accessToken>>;refreshToken=<<refreshToken>>` (I'm using jwt authentication). My simple test script to do that: ```js const tokens = pw.response.headers .filter((ele) => ele.key === "Set-Cookie") .map((ele) => ele.value.split(";")[0].split("=")); pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]); pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1]) ``` The shortcoming is, you have to add this cookie header for each subsequent authentication required requests.

kerem commented

2026-03-16 19:12:25 +03:00

Author

Owner

@CIenthusiast commented on GitHub (Aug 27, 2024):

I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using "test", and use env value in cookier header with accessToken=<<accessToken>>;refreshToken=<<refreshToken>> (I'm using jwt authentication). My simple test script to do that:
const tokens = pw.response.headers
  .filter((ele) => ele.key === "set-cookie")
  .map((ele) => ele.value.split(";")[0].split("="));
pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]);
pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1])
The shortcoming is, you have to set the cookie header for each subsequent authentication required requests.

Nice job. I already looked into the Pre-Request scripts to automate it myself. Just saying that if Hoppscotch wants to be the Postman-Killer it needs this badly. My team wanted to switch due to the problematic privacypolicy of Postman and this is in our way.

@CIenthusiast commented on GitHub (Aug 27, 2024): > I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using "test", and use env value in cookier header with `accessToken=<<accessToken>>;refreshToken=<<refreshToken>>` (I'm using jwt authentication). My simple test script to do that: > > ```js > const tokens = pw.response.headers > .filter((ele) => ele.key === "set-cookie") > .map((ele) => ele.value.split(";")[0].split("=")); > pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]); > pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1]) > ``` > > The shortcoming is, you have to set the cookie header for each subsequent authentication required requests. Nice job. I already looked into the Pre-Request scripts to automate it myself. Just saying that if Hoppscotch wants to be the Postman-Killer it needs this badly. My team wanted to switch due to the problematic privacypolicy of Postman and this is in our way.

kerem commented

2026-03-16 19:12:30 +03:00

Author

Owner

@devNull2and1 commented on GitHub (Aug 27, 2024):

I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using "test", and use env value in cookier header with accessToken=<<accessToken>>;refreshToken=<<refreshToken>> (I'm using jwt authentication). My simple test script to do that:
const tokens = pw.response.headers
  .filter((ele) => ele.key === "set-cookie")
  .map((ele) => ele.value.split(";")[0].split("="));
pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]);
pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1])
The shortcoming is, you have to set the cookie header for each subsequent authentication required requests.
Nice job. I already looked into the Pre-Request scripts to automate it myself. Just saying that if Hoppscotch wants to be the Postman-Killer it needs this badly. My team wanted to switch due to the problematic privacypolicy of Postman and this is in our way.

Dude, wanted to say the same.

@devNull2and1 commented on GitHub (Aug 27, 2024): > > I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using "test", and use env value in cookier header with `accessToken=<<accessToken>>;refreshToken=<<refreshToken>>` (I'm using jwt authentication). My simple test script to do that: > > ```js > > const tokens = pw.response.headers > > .filter((ele) => ele.key === "set-cookie") > > .map((ele) => ele.value.split(";")[0].split("=")); > > pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]); > > pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1]) > > ``` > > > > > > > > > > > > > > > > > > > > > > > > The shortcoming is, you have to set the cookie header for each subsequent authentication required requests. > > Nice job. I already looked into the Pre-Request scripts to automate it myself. Just saying that if Hoppscotch wants to be the Postman-Killer it needs this badly. My team wanted to switch due to the problematic privacypolicy of Postman and this is in our way. Dude, wanted to say the same.

kerem commented

2026-03-16 19:12:35 +03:00

Author

Owner

@Paper-Folding commented on GitHub (Aug 27, 2024):

And since Hoppscotch is written in electron, and "test" block is written in js, you can use console.log in test block, and values will show in Hoppscotch's dev tool, for deugging purpose.

@Paper-Folding commented on GitHub (Aug 27, 2024): And since Hoppscotch is written in electron, and "test" block is written in js, you can use `console.log` in test block, and values will show in Hoppscotch's dev tool, for deugging purpose.

kerem commented

2026-03-16 19:12:41 +03:00

Author

Owner

@wicol commented on GitHub (Oct 14, 2024):

And since Hoppscotch is written in electron, and "test" block is written in js, you can use console.log in test block, and values will show in Hoppscotch's dev tool, for deugging purpose.

I can't find anything called dev tool. How do I look at console output from the test script when using the desktop app?

@wicol commented on GitHub (Oct 14, 2024): > And since Hoppscotch is written in electron, and "test" block is written in js, you can use `console.log` in test block, and values will show in Hoppscotch's dev tool, for deugging purpose. I can't find anything called dev tool. How do I look at console output from the test script when using the desktop app?

kerem commented

2026-03-16 19:12:46 +03:00

Author

Owner

@allen-liaoo commented on GitHub (Oct 17, 2024):

Has the feature of automatically setting cookies from response headers been implemented on the desktop yet? I'm looking to replace postman with this but this is unusable without automatic cookie setter and auth custom redirect_uri

@allen-liaoo commented on GitHub (Oct 17, 2024): Has the feature of automatically setting cookies from response headers been implemented on the desktop yet? I'm looking to replace postman with this but this is unusable without automatic cookie setter and auth custom redirect_uri

kerem commented

2026-03-16 19:12:51 +03:00

Author

Owner

@community-release commented on GitHub (Dec 6, 2024):

Is there any updates on this ?

@community-release commented on GitHub (Dec 6, 2024): Is there any updates on this ?

kerem commented

2026-03-16 19:12:56 +03:00

Author

Owner

@ysomad commented on GitHub (Dec 16, 2024):

Is there any plans on implementing it soon?

@ysomad commented on GitHub (Dec 16, 2024): Is there any plans on implementing it soon?

kerem commented

2026-03-16 19:13:01 +03:00

Author

Owner

@khanhquocnguyen commented on GitHub (Jan 24, 2025):

Any update on this? This is a must have for every api tool

@khanhquocnguyen commented on GitHub (Jan 24, 2025): Any update on this? This is a must have for every api tool

kerem commented

2026-03-16 19:13:06 +03:00

Author

Owner

@perevernihata commented on GitHub (Jan 25, 2025):

This issue is exactly the reason we are not able to switch from postman

@perevernihata commented on GitHub (Jan 25, 2025): This issue is exactly the reason we are not able to switch from postman

kerem commented

2026-03-16 19:13:11 +03:00

Author

Owner

@miku4j commented on GitHub (Feb 3, 2025):

This is diabolical

@miku4j commented on GitHub (Feb 3, 2025): This is diabolical

kerem commented

2026-03-16 19:13:16 +03:00

Author

Owner

@hoaxnerd commented on GitHub (Feb 3, 2025):

Any update on this ?

@hoaxnerd commented on GitHub (Feb 3, 2025): Any update on this ?

kerem commented

2026-03-16 19:13:21 +03:00

Author

Owner

@thiagocavalcanti commented on GitHub (Feb 14, 2025):

I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using hoppscotch's "test" tab, and use env value in cookie header with accessToken=<<accessToken>>;refreshToken=<<refreshToken>> (I'm using jwt authentication). My simple test script to do that:

const tokens = pw.response.headers
.filter((ele) => ele.key === "Set-Cookie")
.map((ele) => ele.value.split(";")[0].split("="));
pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]);
pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1])
The shortcoming is, you have to add this cookie header for each subsequent authentication required requests.

Thanks, this idea solves the issue opened of setting the cookie into next requests, however in my pw.response.headers is still returning only 1 set-cookie header :(

@thiagocavalcanti commented on GitHub (Feb 14, 2025): > I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using hoppscotch's "test" tab, and use env value in cookie header with `accessToken=<<accessToken>>;refreshToken=<<refreshToken>>` (I'm using jwt authentication). My simple test script to do that: > > const tokens = pw.response.headers > .filter((ele) => ele.key === "Set-Cookie") > .map((ele) => ele.value.split(";")[0].split("=")); > pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]); > pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1]) > The shortcoming is, you have to add this cookie header for each subsequent authentication required requests. Thanks, this idea solves the issue opened of setting the cookie into next requests, however in my pw.response.headers is still returning only 1 set-cookie header :(

kerem commented

2026-03-16 19:13:26 +03:00

Author

Owner

@Paper-Folding commented on GitHub (Feb 14, 2025):

I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using hoppscotch's "test" tab, and use env value in cookie header with accessToken=<<accessToken>>;refreshToken=<<refreshToken>> (I'm using jwt authentication). My simple test script to do that:
const tokens = pw.response.headers
.filter((ele) => ele.key === "Set-Cookie")
.map((ele) => ele.value.split(";")[0].split("="));
pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]);
pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1])
The shortcoming is, you have to add this cookie header for each subsequent authentication required requests.

Thanks, this idea solves the issue opened of setting the cookie into next requests, however in my pw.response.headers is still returning only 1 set-cookie header :(

this script just needs modifying to adapt to your implementation

@Paper-Folding commented on GitHub (Feb 14, 2025): > > I found an alternative way, just set accessToken and refreshToken into env variables in your authentication api using hoppscotch's "test" tab, and use env value in cookie header with `accessToken=<<accessToken>>;refreshToken=<<refreshToken>>` (I'm using jwt authentication). My simple test script to do that: > > const tokens = pw.response.headers > > .filter((ele) => ele.key === "Set-Cookie") > > .map((ele) => ele.value.split(";")[0].split("=")); > > pw.env.set("accessToken", tokens.find((ele) => ele[0] === "accessToken")[1]); > > pw.env.set("refreshToken", tokens.find((ele) => ele[0] === "refreshToken")[1]) > > The shortcoming is, you have to add this cookie header for each subsequent authentication required requests. > > Thanks, this idea solves the issue opened of setting the cookie into next requests, however in my pw.response.headers is still returning only 1 set-cookie header :( this script just needs modifying to adapt to your implementation

kerem commented

2026-03-16 19:13:31 +03:00

Author

Owner

@khanhquocnguyen commented on GitHub (Mar 19, 2025):

A year passed and this issue still be there?

@khanhquocnguyen commented on GitHub (Mar 19, 2025): A year passed and this issue still be there?

kerem commented

2026-03-16 19:13:36 +03:00

Author

Owner

@lucasfoussier commented on GitHub (Mar 26, 2025):

+1 This feature would be highly appreciated.

In the case of an API that uses token-based authentication with the token stored in an HTTP-only cookie, it's not possible to use techniques involving Authorization headers (for security reasons).

In the web version of Hoppscotch, this works because the browser acts as the cookie manager and automatically sends the token with subsequent authenticated requests.

Unfortunately, in the desktop version, the only way to authenticate while respecting the API's design is to manually extract the token from the Set-Cookie response header and add it to Hoppscotch's cookie manager. This becomes tedious, especially when dealing with frequently expiring tokens.

@lucasfoussier commented on GitHub (Mar 26, 2025): +1 This feature would be highly appreciated. In the case of an API that uses token-based authentication with the token stored in an HTTP-only cookie, it's not possible to use techniques involving Authorization headers (for security reasons). In the web version of Hoppscotch, this works because the browser acts as the cookie manager and automatically sends the token with subsequent authenticated requests. Unfortunately, in the desktop version, the only way to authenticate while respecting the API's design is to manually extract the token from the Set-Cookie response header and add it to Hoppscotch's cookie manager. This becomes tedious, especially when dealing with frequently expiring tokens.

kerem commented

2026-03-16 19:13:42 +03:00

Author

Owner

@kawpii commented on GitHub (Mar 26, 2025):

Just found out this, this is really necessary.

@kawpii commented on GitHub (Mar 26, 2025): Just found out this, this is really necessary.

kerem commented

2026-03-16 19:13:47 +03:00

Author

Owner

@amishratnasthapit commented on GitHub (Mar 28, 2025):

This is the last feature I need to migrate my company to Hoppscotch. All our APIs now use Server Side Cookie and without this feature using Hoppscotch is very brutal.

@amishratnasthapit commented on GitHub (Mar 28, 2025): This is the last feature I need to migrate my company to Hoppscotch. All our APIs now use Server Side Cookie and without this feature using Hoppscotch is very brutal.

kerem commented

2026-03-16 19:13:52 +03:00

Author

Owner

@FerreiraAdrien commented on GitHub (Apr 14, 2025):

Same as above, this is the last feature I need in Hoppscotch before I can fully migrate. If you have any roadmap or estimated timeline for it, that would be really helpful and a big time-saver.

@FerreiraAdrien commented on GitHub (Apr 14, 2025): Same as above, this is the last feature I need in Hoppscotch before I can fully migrate. If you have any roadmap or estimated timeline for it, that would be really helpful and a big time-saver.

kerem commented

2026-03-16 19:13:57 +03:00

Author

Owner

@amnbcw commented on GitHub (May 22, 2025):

Wow. This is still not implemented? Jeez

@amnbcw commented on GitHub (May 22, 2025): Wow. This is still not implemented? Jeez

kerem commented

2026-03-16 19:14:02 +03:00

Author

Owner

@rjmcloudh commented on GitHub (May 28, 2025):

Any update?

@rjmcloudh commented on GitHub (May 28, 2025): Any update?

kerem commented

2026-03-16 19:14:07 +03:00

Author

Owner

@makkmarci13 commented on GitHub (Jun 5, 2025):

Any update?

@makkmarci13 commented on GitHub (Jun 5, 2025): Any update?

kerem commented

2026-03-16 19:14:12 +03:00

Author

Owner

@srkhost commented on GitHub (Jun 5, 2025):

Any update?

@srkhost commented on GitHub (Jun 5, 2025): Any update?

kerem commented

2026-03-16 19:14:17 +03:00

Author

Owner

@peem041045 commented on GitHub (Jun 24, 2025):

Any update?

@peem041045 commented on GitHub (Jun 24, 2025): Any update?

kerem commented

2026-03-16 19:14:22 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jun 24, 2025):

I completely understand your frustration. Historically, Hoppscotch was a web-first platform, and due to the limitations of web-based cookies access from browsers, we couldn’t implement set-cookie from response.

However, we hope to add support for this in our desktop app, which is capable of doing so. This might be a bit complex and require a relatively high bandwidth and resources from our small team. Nevertheless, it’s in our roadmap. We’re always open to contributions, so if you’d like to help, we’d be happy to review a PR!

Originally posted by @liyasthomas in #5188

@liyasthomas commented on GitHub (Jun 24, 2025): > I completely understand your frustration. Historically, Hoppscotch was a web-first platform, and due to the limitations of web-based cookies access from browsers, we couldn’t implement set-cookie from response. > > However, we hope to add support for this in our desktop app, which is capable of doing so. This might be a bit complex and require a relatively high bandwidth and resources from our small team. Nevertheless, it’s in our roadmap. We’re always open to contributions, so if you’d like to help, we’d be happy to review a PR! _Originally posted by @liyasthomas in [#5188](https://github.com/hoppscotch/hoppscotch/issues/5188#issuecomment-2996761118)_

kerem commented

2026-03-16 19:14:27 +03:00

Author

Owner

@CIenthusiast commented on GitHub (Jun 25, 2025):

Maybe you should consider a bounty to encourage people to commit.
Nothing changed the last 2 years, nothing will change in the next 2 years.
And IMO this should be a top priority. In my case there is no use for hoppscotch unless this functionality is implemented.

@CIenthusiast commented on GitHub (Jun 25, 2025): Maybe you should consider a bounty to encourage people to commit. Nothing changed the last 2 years, nothing will change in the next 2 years. And IMO this should be a top priority. In my case there is no use for hoppscotch unless this functionality is implemented.

kerem commented

2026-03-16 19:14:32 +03:00

Author

Owner

@Gybk commented on GitHub (Sep 18, 2025):

@Gybk commented on GitHub (Sep 18, 2025): +

kerem commented

2026-03-16 19:14:38 +03:00

Author

Owner

@lucasfoussier commented on GitHub (Sep 25, 2025):

Hello everyone, do we have any updates regarding this issue?

@lucasfoussier commented on GitHub (Sep 25, 2025): Hello everyone, do we have any updates regarding this issue?

kerem commented

2026-03-16 19:14:43 +03:00

Author

Owner

@liyasthomas commented on GitHub (Sep 25, 2025):

This issue will be fixed in next release candidate scheduled for end of month.

@liyasthomas commented on GitHub (Sep 25, 2025): This issue will be fixed in next release candidate scheduled for end of month.

kerem commented

2026-03-16 19:14:48 +03:00

Author

Owner

@arthartn commented on GitHub (Sep 30, 2025):

Hello everyone, has this been resolved in the latest version 2025.9.0 ?

We tried logging in (on our localhost) using the desktop app (2025.9.0) on Mac, and the cookie was returned successfully.
However, when trying to get the authentication status afterwards (the same or another tab - both GET requests), the app (presumably) fails to send the cookie to the server, and we get 'Not authorized' (as before), although the cookie is there and not expired, thus, should return the logged-in user.

Are there any settings to be changed/updated to make this work (automatically) ?

@arthartn commented on GitHub (Sep 30, 2025): Hello everyone, has this been resolved in the latest version 2025.9.0 ? We tried logging in (on our localhost) using the desktop app (2025.9.0) on Mac, and the cookie was returned successfully. However, when trying to get the authentication status afterwards (the same or another tab - both GET requests), the app (presumably) fails to send the cookie to the server, and we get 'Not authorized' (as before), although the cookie is there and not expired, thus, should return the logged-in user. Are there any settings to be changed/updated to make this work (automatically) ?

kerem commented

2026-03-16 19:14:53 +03:00

Author

Owner

@liyasthomas commented on GitHub (Sep 30, 2025):

This issue ticket has two main parts:

Only single Set-Cookie in response - fixed in #5394.
The inability to transmit those cookies to subsequent requests.

The first issue has been resolved in the latest release. We are actively working towards resolving the second issue. This issue is not specific to the desktop app but affects web applications in general. It may involve changes to both backend and frontend components, which we are working towards implementing.

I will keep this ticket open until the functionality to send cookies along with requests for the app is available.

@liyasthomas commented on GitHub (Sep 30, 2025): This issue ticket has two main parts: 1. Only single Set-Cookie in response - fixed in #5394. 2. The inability to transmit those cookies to subsequent requests. The first issue has been resolved in the latest release. We are actively working towards resolving the second issue. This issue is not specific to the desktop app but affects web applications in general. It may involve changes to both backend and frontend components, which we are working towards implementing. I will keep this ticket open until the functionality to send cookies along with requests for the app is available.

kerem commented

2026-03-16 19:14:58 +03:00

Author

Owner

@mathew2103 commented on GitHub (Jan 15, 2026):

More than 2 years since this issue was opened, please look into fixing this

@mathew2103 commented on GitHub (Jan 15, 2026): More than 2 years since this issue was opened, please look into fixing this

kerem referenced this issue

2026-03-17 00:46:33 +03:00

[PR #1205] [MERGED] upstream #3135

kerem referenced this issue

2026-03-17 00:46:49 +03:00

[PR #1207] [MERGED] I18n #3140