From b5bb240439530bd5ae6a7e89af31e9f492d06625 Mon Sep 17 00:00:00 2001 From: Demis Bellot Date: Thu, 12 Sep 2024 12:09:49 +0800 Subject: [PATCH] cleanup --- MyApp/_pages/background-jobs.md | 14 +++++++------- MyApp/_pages/releases/v8_04.md | 14 +++++++------- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/MyApp/_pages/background-jobs.md b/MyApp/_pages/background-jobs.md index 11f14e90aa..5ab7c795af 100644 --- a/MyApp/_pages/background-jobs.md +++ b/MyApp/_pages/background-jobs.md @@ -669,33 +669,33 @@ public class NotifyCheckUrlsCommand(IHttpClientFactory clientFactory) `ReplyTo` can be any URL which by default will have the result POST'ed back to the URL with a JSON Content-Type. Typically URLs will contain a reference Id so external clients can correlate a callback with the internal process that initiated the job. If the callback API is publicly available you'll -want to use an internal Id that can't be guessed so the callback can't be spoofed like a Guid, e.g: +want to use an internal Id that can't be guessed so the callback can't be spoofed, like a Guid, e.g: `$"https://api.example.com?refId={RefId}"` -If needed the callback URL can be customized on how the HTTP Request is sent: +If needed the callback URL can be customized on how the HTTP Request callback is sent. If the URL contains a space, the text before the space is treated as the HTTP method: `"PUT https://api.example.com"` -If the auth part contains a colon :, it's treated as Basic Auth. +If the auth part contains a colon `:` it's treated as Basic Auth: `"username:password@https://api.example.com"` -If name starts with 'http.' sends a HTTP Header +If name starts with `http.` sends a HTTP Header `"http.X-API-Key:myApiKey@https://api.example.com"` -Otherwise used as Bearer Token: +Otherwise it's sent as a Bearer Token: `"myToken123@https://api.example.com"` -Bearer Token or HTTP Headers starting with '$' is substituted with Environment Variable if exists +Bearer Token or HTTP Headers starting with `$` is substituted with Environment Variable if exists: `"$API_TOKEN@https://api.example.com"` -When needed headers, passwords and tokens can be URL encoded if they contain any delimiter characters. +When needed headers, passwords and tokens can be URL encoded if they contain any delimiter characters. ## Implementing Commands diff --git a/MyApp/_pages/releases/v8_04.md b/MyApp/_pages/releases/v8_04.md index e42e09cfe0..b65e052580 100644 --- a/MyApp/_pages/releases/v8_04.md +++ b/MyApp/_pages/releases/v8_04.md @@ -687,33 +687,33 @@ public class NotifyCheckUrlsCommand(IHttpClientFactory clientFactory) `ReplyTo` can be any URL which by default will have the result POST'ed back to the URL with a JSON Content-Type. Typically URLs will contain a reference Id so external clients can correlate a callback with the internal process that initiated the job. If the callback API is publicly available you'll -want to use an internal Id that can't be guessed so the callback can't be spoofed like a Guid, e.g: +want to use an internal Id that can't be guessed so the callback can't be spoofed, like a Guid, e.g: `$"https://api.example.com?refId={RefId}"` -If needed the callback URL can be customized on how the HTTP Request is sent: +If needed the callback URL can be customized on how the HTTP Request callback is sent. If the URL contains a space, the text before the space is treated as the HTTP method: `"PUT https://api.example.com"` -If the auth part contains a colon :, it's treated as Basic Auth. +If the auth part contains a colon `:` it's treated as Basic Auth: `"username:password@https://api.example.com"` -If name starts with 'http.' sends a HTTP Header +If name starts with `http.` sends a HTTP Header `"http.X-API-Key:myApiKey@https://api.example.com"` -Otherwise used as Bearer Token: +Otherwise it's sent as a Bearer Token: `"myToken123@https://api.example.com"` -Bearer Token or HTTP Headers starting with '$' is substituted with Environment Variable if exists +Bearer Token or HTTP Headers starting with `$` is substituted with Environment Variable if exists: `"$API_TOKEN@https://api.example.com"` -When needed headers, passwords and tokens can be URL encoded if they contain any delimiter characters. +When needed headers, passwords and tokens can be URL encoded if they contain any delimiter characters. ## Implementing Commands