Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typo in Token docs #5781

Merged
merged 1 commit into from Apr 15, 2024
Merged

Fix typo in Token docs #5781

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions lib/phoenix/token.ex
View file
Open in desktop
Expand Up @@ -4,14 +4,14 @@ defmodule Phoenix.Token do
for use in Channels, API authentication, and more.

The data stored in the token is signed to prevent tampering, and is
optionally encrypted. This means that, so long as the
optionally encrypted. This means that, so long as the
key (see below) remains secret, you can be assured that the data
stored in the token has not been tampered with by a third party.
However, unless the token is encrypted, it is not safe to use this
token to store private information, such as a user's sensitive
identification data, as it can be trivially decoded. If the
token is encrypted, its contents will kept secret from the client,
but it is still a best practice to encode as little secret
token is encrypted, its contents will be kept secret from the
client, but it is still a best practice to encode as little secret
information as possible, to minimize the impact of key leakage.

## Example
Expand Down