Chrome version adds cookie to parent domain
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
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from JetBrains/xdebug-extension
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JetBrains/xdebug-extension#60 · 5 comments ·
-
Firefox JSON viewer not loading content scriptsPossibly taken @GtechGovind claimed this 73 days ago. Openhelp wanted
Difficulty 3/5 1-2 days Newbie friendliness 55/100
JetBrains/xdebug-extension#51 · 1 reaction ·
-
Support for Different DomainsMay be free again @FraserChapman claimed this 253 days ago, and no pull request is open. Openhelp wanted
JetBrains/xdebug-extension#32 · 1 comment · 2 reactions · 1 assignee ·
-
Safari supportPossibly taken @FraserChapman claimed this 572 days ago. Openenhancement mac
JetBrains/xdebug-extension#28 · 4 comments · 1 reaction · 1 assignee ·
All issues in JetBrains/xdebug-extension
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Needs: Author Feedback Needs: Repro
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
react/react-native#60059 · 1 comment ·
Maintainers usually reply within 2 days
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
mastra-ai/mastra#30587 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
embedpdf/embed-pdf-viewer#1098 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Tudmotu/gnome-shell-extension-clipboard-indicator#673 ·
Maintainers usually reply within 11 days