Cross-site request error in Chrome console when dashboard calls linkerd.io
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
The Linkerd2 dashboard calls `versioncheck.linkerd.io` upon opening, to check if the user is running the latest version of Linkerd. The Chrome console has begun showing these alerts in the console after making the version check:
Text:
```
A cookie associated with a cross-site resource at https://linkerd.io/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
```
These are triggered by `versioncheck.linkerd.io` and by opening the Community Updates iFrame.
Contributor 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.
Research direction
Start by reproducing the Chrome console warnings while opening the dashboard, checking the versioncheck.linkerd.io request and the Community Updates iframe. Trace where the linkerd.io cookies are configured; done means the cross-site cookie warnings no longer appear in Chrome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100