Skip to content

Commit 9e5da3d

Browse files
committed
Update readme
1 parent f62c5e7 commit 9e5da3d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ All POST and PATCH requests will now be idempotent using the `Idempotency-Key` H
6161

6262
### Persisted store
6363

64-
The ETS store is not persisted, so it's not production ready. Instead, let's change the store to use Ecto.
64+
The ETS store is not persisted, so it's not production-ready. Instead, let's change the store to use Ecto.
6565

6666
First, run `mix idempotency_plug.ecto.gen.migration`.
6767

@@ -73,7 +73,7 @@ Now update the configuration for the request tracker:
7373

7474
You can also implement your own idempotent request store by using the behaviour in `IdempotencyPlug.Store`.
7575

76-
## Scope `Idempotency-Key`
76+
## Scope `Idempotency-Key` to authenticated user
7777

7878
If you are authenticating users then you must scope the `Idempotency-Key` to the authenticated user:
7979

@@ -85,7 +85,7 @@ plug IdempotencyPlug,
8585
def scope_idempotency_key(conn, key), do: {conn.assigns.current_user.id, key}
8686
```
8787

88-
Otherwise, you may have a security vulnerability (or conflict) where any user can access another user's cached responses when requests are identical.
88+
If you do not do this, you may have a security vulnerability (or conflict) where any user can access another user's cached responses when requests are identical.
8989

9090
## Customize error response
9191

0 commit comments

Comments
 (0)