chore: update

Author: czy88840616

README.md

@@ -10,7 +10,7 @@ More encryption than the original version, using a more secure aes-256-gcm algor
 
 ```ts
 import * as Cookies from '@midwayjs/cookies');
-ctx.cookies = new Cookies(ctx, keys[, defaultCookieOptions]);
+ctx.cookies = new Cookies(ctx, keys[, defaultCookieOptions[, defaultGetCookieOptions]]);
 ctx.cookies.set('foo', 'bar', { encrypt: true });
 ctx.cookies.get('foo', { encrypt: true });
 ```
@@ -41,6 +41,15 @@ Read a cookie through `cookies.get(key, value, options)`. The parameters support
 - signed - Whether `Boolean` needs to verify the cookie, and pass the signed parameter when cooperating with the set. At this time, the front-end cannot tamper with the cookie. The default is true.
 - encrypt - Whether `Boolean` needs to decrypt the cookie, and pass the encrypt parameter when cooperating with the set. At this time, the front-end cannot read the real cookie value, and the default is false.
 
+You can also set default options for `get` method by passing `defaultGetCookieOptions` when initializing Cookies:
+
+```ts
+const cookies = new Cookies(ctx, keys, defaultCookieOptions, { signed: false });
+// Now cookies.get('foo') will use signed: false by default
+```
+
+**⚠️ Security Warning: Setting `signed: false` in `defaultGetCookieOptions` is dangerous as it disables cookie signature verification by default. This makes your application vulnerable to cookie tampering attacks. Only use this option if you fully understand the security implications and have a specific reason to disable signature verification.**
+
 ## Delete cookie
 
 Use `cookie.set(key, null)` to delete a cookie. If the `signed` parameter is passed, the signature will also be deleted.

README.zh_CN.md

@@ -10,7 +10,7 @@
 
 ```ts
 import * as Cookies from '@midwayjs/cookies');
-ctx.cookies = new Cookies(ctx, keys[, defaultCookieOptions]);
+ctx.cookies = new Cookies(ctx, keys[, defaultCookieOptions[, defaultGetCookieOptions]]);
 ctx.cookies.set('foo', 'bar', { encrypt: true });
 ctx.cookies.get('foo', { encrypt: true });
 ```
@@ -47,6 +47,15 @@ ctx.cookies.get('foo', { encrypt: true });
 - signed - `Boolean` 是否需要对 cookie 进行验签，需要配合 set 时传递 signed 参数，此时前端无法篡改这个 cookie，默认为 true。
 - encrypt - `Boolean` 是否需要对 cookie 进行解密，需要配合 set 时传递 encrypt 参数，此时前端无法读到真实的 cookie 值，默认为 false。
 
+你也可以在初始化 Cookies 时通过 `defaultGetCookieOptions` 参数设置 `get` 方法的默认选项：
+
+```ts
+const cookies = new Cookies(ctx, keys, defaultCookieOptions, { signed: false });
+// 现在 cookies.get('foo') 将默认使用 signed: false
+```
+
+**⚠️ 安全警告：在 `defaultGetCookieOptions` 中设置 `signed: false` 是非常危险的行为，因为它会默认禁用 cookie 签名验证。这会使你的应用容易受到 cookie 篡改攻击。只有在完全理解安全影响并有特定原因需要禁用签名验证的情况下，才应该使用此选项。**
+
 ## 删除 cookie
 
 通过 `cookie.set(key, null)` 来删除一个 cookie。如果传递了 `signed` 参数，签名也会被删除。