From bc66c72b7a4dd028b036873e8dda9ceea562fcd1 Mon Sep 17 00:00:00 2001 From: Ike McCreery Date: Mon, 22 Jan 2024 20:02:39 -0500 Subject: [PATCH] Fix comments about csrf_state (#245) Fixes #208. Co-authored-by: Ike McCreery --- src/lib.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/lib.rs b/src/lib.rs index 10a17be..0e9aa13 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -131,7 +131,7 @@ //! //! // Once the user has been redirected to the redirect URL, you'll have access to the //! // authorization code. For security reasons, your code should verify that the `state` -//! // parameter returned by the server matches `csrf_state`. +//! // parameter returned by the server matches `csrf_token`. //! //! // Now you can trade it for an access token. //! let token_result = @@ -202,7 +202,7 @@ //! //! // Once the user has been redirected to the redirect URL, you'll have access to the //! // authorization code. For security reasons, your code should verify that the `state` -//! // parameter returned by the server matches `csrf_state`. +//! // parameter returned by the server matches `csrf_token`. //! //! // Now you can trade it for an access token. //! let token_result = client @@ -259,7 +259,7 @@ //! //! // Once the user has been redirected to the redirect URL, you'll have the access code. //! // For security reasons, your code should verify that the `state` parameter returned by the -//! // server matches `csrf_state`. +//! // server matches `csrf_token`. //! //! # Ok(()) //! # }