From c296530d15560b5139390ad9780941a706d65114 Mon Sep 17 00:00:00 2001 From: arnold Date: Fri, 30 Aug 2024 14:32:53 +0200 Subject: [PATCH] Update NPM api key for Travis deploy Documentation fixes --- .travis.yml | 2 +- docs/signing/browser.md | 6 ++++-- docs/signing/index.md | 5 +++-- docs/signing/nodejs.md | 5 +++-- 4 files changed, 11 insertions(+), 7 deletions(-) diff --git a/.travis.yml b/.travis.yml index 40876b0..3637967 100644 --- a/.travis.yml +++ b/.travis.yml @@ -64,7 +64,7 @@ jobs: provider: npm email: arnold@jasny.net api_key: - secure: "gOTMGI6t3OYUJZX1iWYZOH/3L8KjmptGRrJtNIybxmtfYtpj240roO7VMixUWQ+e+5Lfi8q2OVkQB+Y6kVS3RMoTHFqXCyQSqNOPC6rL57HvmNXbwTc9rxLr97yrVJGz4M5yz6VLHxygUeEG81ntQPNsc1nVvF34RvYaS4xkK/YHJkiukyxFgf90Rjv8HYIOMzttVFAT2sTbyj1h1SjeNcRDO2aVAaA6VHSAOUb9X0LFdIFxq2jdjp1XK/RZ7y2YRHVSXc2EFl1HXy3uSEvgYjgesCv7/bDEHKxz9wJ4QuBf1wsyEh1SrZev3yFQ/TrP7FHXAS92aLJ9NUvydDVr82VKXrLvz4Hbj3luF0PfcBpJbT7RV9Dsot+2jV4zq2AIMd7xazeee9d0/FRG7NaUSQHqHklK/wbM6PwjFmRpMdXrp5NQSweWPpu/QURodOYc5QcuM+szODDAvheoiXczAPK5PEPqOQylWkcC+gJAPiRbOXvvQmN2Vbiv2BEYUv/gwtBA2ftNlK53o8GW4r7jO9SgaM7wjarycmioUo8KugkpO1AKZidhKp8J5tHQ4vAbfc1d5Ck5xp1M2JL48aVlJKPhj4HTfsJKHsPeeOPa02ePqbC42ROuznZeTtYX7jF54rXcb0rpGCyxmnr5FY3nzwUMkLFCcv5CEYlWQI/qLio=" + secure: "rLJx3dLxxSQ/Exv1TMtnqwzJhXIA3T33orDnargxkjHuqbfVj9S3l/O0wxAKHjZgfujkponcwmeAidYocjrPWXCJqIkgZ7rCegkg3Vf6nOF4mojzE3uKaU2T3bgLzUobjYzjuxTvzDHEOXRIwpJqvEwyV6NQ5DPnmlodlocnk+zmJo68FZgW7tH+W9QDWK9DmUYsFwwQ00qaFNXLtzcxUFk8WqJwufQ4rJEsPSMqnCLXJCvZ5+mHsXIxiunMo3oA6ogRYhlYN6L5EtuqGmT+DBdj7bnKpVI3wBDKlghN+zAbhVTSQ9ZhIRjiSGZ7uSOtWD5eNQChVYVRzdGy/OElxlmgmUl7mBhacRmHJRyNjfy4Umas2+DRO3mJSdUY5jClu4qU2jt5EjknA79sFrBee6KKaZvxl3+bJK3qVYVa5EwrPl2j4eVcfcTMuB2Ls8s6SEsHKBkderRfIiRnl3CfUzaUtI7K/mHzZg4Xs/UNNUNkSHtkzgK0fKHkn+/E4qa4Z54+pcoPJ0orxc/neUDRhMhST5Y5u4ImuUWhVIUNYm0aWA2s8mKf5C75G5mifPBiMrprKgx0N4yndsPYCVaOP94iqQD4rYhBYZN8K1XjM0stSXcwj7TB704s3cQnCmIWqhydKBbhoCMNO24d591kEUTQTKEJBg/yEgoJ1ilD6L4=" on: tags: true cleanup: false diff --git a/docs/signing/browser.md b/docs/signing/browser.md index a9945e9..aa34cba 100644 --- a/docs/signing/browser.md +++ b/docs/signing/browser.md @@ -71,8 +71,9 @@ You can specify the components to sign using the `components` option. For more i ### Digest To secure the integrity of the HTTP request or response body, you can use the -[`Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Digest). This header contains a hash of the -message body. +[`Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Digest) or +[`Content-Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Digest). This header +contains a hash of the message body. Before signing the HTTP message, you'll need to create the digest and add it to the headers. To create a Digest header using the SHA-256 hashing algorithm and the SubtleCrypto API: @@ -114,3 +115,4 @@ const components = ['@status', 'content-type', 'digest']; // ... Send the signed response to the client })(); ``` + diff --git a/docs/signing/index.md b/docs/signing/index.md index 8ab4471..1703046 100644 --- a/docs/signing/index.md +++ b/docs/signing/index.md @@ -148,8 +148,9 @@ Digest: SHA-256=4VYMyeX0tNLQ7opuAJeMECP3HgfLswAG3n+IqQprO0Q= ### Content-Digest -The `Content-Digest` header is defined in the [draft-ietf-httpbis-digest-headers-11](https://www.ietf.org/archive/id/draft-ietf-httpbis-digest-headers-11.html), -which aims to obsolete the current RFC 3230 standard, which defines the `Digest` header. +The [`Content-Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Digest) is defined in the +[draft-ietf-httpbis-digest-headers-13](https://www.ietf.org/archive/id/draft-ietf-httpbis-digest-headers-13.html). It aims +to replace the current RFC 3230 standard, which defines the `Digest` header. It serves a similar purpose as the `Digest` header for message integrity. However, since the draft has not yet become an official standard, this guide uses the `Digest` header for broader compatibility and adherence to the currently diff --git a/docs/signing/nodejs.md b/docs/signing/nodejs.md index 3ea9ac0..26ecb3f 100644 --- a/docs/signing/nodejs.md +++ b/docs/signing/nodejs.md @@ -69,8 +69,9 @@ You can specify the components to sign using the `components` option. For more i ### Digest To secure the integrity of the HTTP request or response body, you can use the -[`Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Digest). This header contains a hash of the -message body. +[`Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Digest) or +[`Content-Digest` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Digest). This header +contains a hash of the message body. Before signing the HTTP message, you'll need to create the digest and add it to the headers. To create a Digest header using the SHA-256 hashing algorithm and the `crypto` library: