Chrome version adds cookie to parent domain

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

@GtechGovind is already working on this.

Since Sep 3, 2026.

  • #61 by @GtechGovind — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
devtools

Research direction

Start by reproducing the cookie behavior in Chrome 148 on macOS with a site at xxx.yyy.zzz, then inspect the extension's cookie handling entry point. Verify that enabling Debug mode creates only a cookie for the accessed domain and that disabling it removes that cookie without leaving a parent-domain cookie.

Written by the indexing model from the issue text.

Description

help wanted

Describe the bug
When enable Debug mode (haven't tried other modes) in Chrome v148.0 (Mac) the domain for the cookie is set to wildcard of parent domain. After page reload a 2nd cookie with domain is then set correct to the domain being accessed, but also includes the cookie for the wildcard of parent domain, thereby 2 cookies are set. This 2nd cookie is likely set by PHP on the site.

When disable Debug mode the cookie for the current domain is removed but the cookie for domain of wildcat parent remains and must be manually removed.

In Firefox v140.11 (Mac) initially enabling Debug mode does not set cookie domain to wildcard of parent domain.

To Reproduce
Load page from site xxx.yyy.zzz
View cookies stored in browser
Enable Debug mode
View cookies stored in browser will see domain for XDEBUG_SESSION cookie is set to ".yyy.zzz" (wildcard parent domain)
Reload page.
View cookies stored in browser, will see 2 XDEBUG_SESSION cookies.
Disable Debug mode
View cookies stored in browser, will see 1 cookie with domain set to ".yyy.zzz"

Expected behavior
Enable Debug mode should not set cookie domain as wildcard of parent domain.

Screenshots
Not needed

Desktop (please complete the following information):

  • OS: Mac OS
  • Browser Chrome v148.0, Firefox v140.11
  • Version [e.g. 22]

Smartphone (please complete the following information):
None tested

Additional context
Have not tested other browsers.

Dominant language
JavaScript
Stars
137
Forks
16
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JetBrains/xdebug-extension

All issues in JetBrains/xdebug-extension

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.