RLT proxy for Likes and Notifications #19208
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #15184
Changes proposed in this Pull Request:
Jetpack product discussion
pcNnmV-1L-p2
Does this pull request change what data or activity we track or use?
This provides the browser with a token, known as an RLT or "Remote Login Token", which is used to authorize Like and Notification requests, just like we currently do with cookies. The token is stored in localStorage for the Jetpack site, in the user's browser, and sent with some API requests. The reason for this change is that browsers are increasingly blocking "third-party" cookies - which includes any cookies normally set or sent by cross-origin iframes.
Testing instructions: