This is an automated email from the ASF dual-hosted git repository.
xiaoyu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shenyu-website.git
The following commit(s) were added to refs/heads/main by this push:
new b8872fc337d Fixed some wrong word (#850)
b8872fc337d is described below
commit b8872fc337d3319935ce61b04ff6386ec2ce60a5
Author: 愿凌飞 <[email protected]>
AuthorDate: Tue Jan 17 14:48:34 2023 +0800
Fixed some wrong word (#850)
---
docs/plugin-center/security/sign-plugin.md | 10 +++++-----
.../current/plugin-center/security/sign-plugin.md | 12 ++++++------
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/docs/plugin-center/security/sign-plugin.md
b/docs/plugin-center/security/sign-plugin.md
index be80121b7d2..93c33e137e9 100644
--- a/docs/plugin-center/security/sign-plugin.md
+++ b/docs/plugin-center/security/sign-plugin.md
@@ -244,7 +244,7 @@ This authentication algorithm is the version 2.0.0
algorithm, which is same as v
### 2.5.1 Authentication Guide
-Authentication algorithm of Version 2.0.0 generates a Token based on the
signature algorithm, and puts the Token value into the request header
Authorization parameter when sending a request. To distinguish it from version
1.0.0, the version parameter of the request header is left, which is 2.0.0.
+Authentication algorithm of Version 2.0.0 generates a Token based on the
signature algorithm, and puts the Token value into the request header
`Authorization` parameter when sending a request. To distinguish it from
version 1.0.0, the `version` parameter of the request header is left, which is
2.0.0.
#### 2.5.1.1 prepare
@@ -321,11 +321,11 @@ Authentication algorithm of Version 2.0.0 generates a
Token based on the signatu
-#### 2.6.1.5 Add AppKey/SecretKey
+#### 2.6.1.4 Add AppKey/SecretKey
-#### 2.6.1.6 Request Service and check result
+#### 2.6.1.5 Request Service and check result
* build request params with `Authentication Guide`,
@@ -392,9 +392,9 @@ public class Test2 {
### 2.6.2 Verify api with sign plugin（2.0.0）
-All the configuration parts are the same, so let's look directly at the
parameter part of the calculation request header and the part of sending
request.
+All the configuration parts are the same, so let's look directly at the the
calculation part of parameter of request header and the part of sending request.
-### 2.6.1.1 Request Service and check result
+#### 2.6.2.1 Request Service and check result
- implements the algorithm
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/current/plugin-center/security/sign-plugin.md
b/i18n/zh/docusaurus-plugin-content-docs/current/plugin-center/security/sign-plugin.md
index 09b187f4036..e915702a2b8 100644
---
a/i18n/zh/docusaurus-plugin-content-docs/current/plugin-center/security/sign-plugin.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/current/plugin-center/security/sign-plugin.md
@@ -331,11 +331,11 @@ DigestUtils.md5DigestAsHex(sign.getBytes()).toUpperCase()
-#### 2.6.1.5 添加AppKey/SecretKey
+#### 2.6.1.4 添加AppKey/SecretKey
-#### 2.6.1.6 Request Service and check result
+#### 2.6.1.5 Request Service and check result
* 构造请求参数，请查看`Authentication Guide`目录,
@@ -405,7 +405,7 @@ public class Test2 {
所有配置部分皆相同，我们直接看计算请求头的参数部分和发送请求部分
-### 2.6.1.1 Request Service and check result
+#### 2.6.2.1 Request Service and check result
+ 算法实现
@@ -433,7 +433,7 @@ public class Test2 {
}
```
-+ 不校验请求体演示
++ 不包含请求体校验演示
```java
public static void main(String[] args) {
@@ -467,13 +467,13 @@ public class Test2 {
发送请求：
- ![image-20230114230500887]/img/shenyu/plugin/sign/version2_sign_request.png)
+ 
-+ 校验请求体演示
++ 包含请求体校验演示
计算Token
