Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Undo cookies fails to set a cookie starting with __Secure-

See original GitHub issue

Some cookies which I get back , does have this error: Failed to parse or set a cookie named: __Secure-3PSID, even on the latest version, and dev build as well.

_Originally posted by @Marek33 in

Additional Background Has to do with this:

And for some reason the code didn’t include domain or secure attributes when restoring cookies. Because we didn’t set the secure parameter to true, by MDN’s doc, it is set to false by default.

quick bugfix will be patched shortly.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

kennethtran93commented, Jun 16, 2020

I’ve added a commit to scrub cookieStoreId 1 from cleanup logs as we most likely cannot restore them anyway.

Marek33commented, Jun 17, 2020

The number of all deleted cookies.

If you head to the welcome page, you may be able to see the total cookies removed overall. I don’t think we decrement those count at this time but I could be wrong.

When I click on clearing the cookie entries, in the Cleanup Log, then it gets reset to 0, which I think shouldn’t be.

Open a new issue/feature request for this. Currently does seem that way when I look at the backend.

Yes, I will since I just did that, in Sandboxie on the Firefox.

I see, and I did it by mistake, on the Iridium, but when I use the new version, I don’t have that problem, since I’m using the unpacked version.

From what I can understand, the official version is assigned its extension ID through chrome webstore, while the unpacked version uses a locally randomized extension ID, thus why you would be able to do that I think…Probably the unpacked version follows a separate logic when it comes down to these things…maybe.

No, it’s because I can’t update the extension since Iridium/Ungoogled block that connection, so there is nothing ported from the older versions. I will copy the data (for statistics), but I will not change any settings, so I wouldn’t break it again.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Turn cookies on or off - Computer - Google Account Help
On your computer, open Chrome. · At the top right, click More More and then Settings. · Under "Privacy and security," click Site...
Read more >
This Set-Cookie didn't specify a "SameSite" attribute and was ...
I tried to solve this by making the server use SameSite=None (development only). This causes a different error: Connection isn't secure . This ......
Read more >
Secure Cookie Attribute - OWASP Foundation
Overview. The secure attribute is an option that can be set by the application server when sending a new cookie to the user...
Read more >
How to Enable & Disable Cookies in Your Browser | Avast
Under the Privacy and security section, find the Content settings entry. Click that. To disable cookies, flip off the switch next to Allow ......
Read more >
Set-Cookie - HTTP - MDN Web Docs
__Secure- prefix: Cookies with names starting with __Secure- (dash is part of the prefix) must be set with the secure flag from a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found