From 20c72a3649139889d2f86f872972e4a94182ea38 Mon Sep 17 00:00:00 2001 From: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Date: Thu, 25 Jul 2019 18:56:17 +0100 Subject: [PATCH] Update proposals/2134-identity-hash-lookup.md Co-Authored-By: David Baker --- proposals/2134-identity-hash-lookup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/2134-identity-hash-lookup.md b/proposals/2134-identity-hash-lookup.md index 72bc4e53..1d797086 100644 --- a/proposals/2134-identity-hash-lookup.md +++ b/proposals/2134-identity-hash-lookup.md @@ -161,7 +161,7 @@ M_INVALID_PARAM`. If the pepper does not match the server's, the server should return a new error code, `400 M_INVALID_PEPPER`. A new error code is not defined for an invalid algorithm as that is considered a client bug. -The `M_INVALID_PEPPER` error response contain the correct `algorithm` and +The `M_INVALID_PEPPER` error response contains the correct `algorithm` and `lookup_pepper` fields. This is to prevent the client from needing to query `/hash_details` again, thus saving a request. `M_INVALID_PARAM` does not include these fields. An example response to an incorrect pepper would be: