Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix url-encode syntax and description #11

Merged
merged 1 commit into from
Aug 3, 2023
Merged

Fix url-encode syntax and description #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...ting-messages/customizing-message-format/reference-template-functions/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1291,9 +1291,9 @@ Available in {{% param "product.abbrev" %}} version 3.18 and later.

## url-encode {#template-function-url-encode}

*Syntax:* `$(url-encode ${MESSAGE} )\n")`
*Syntax:* `$(url-encode ${MESSAGE})`

*Description:* You can use the `url-encode` template function together with the `telegram()` destination to send syslog messages to [Telegram.](https://core.telegram.org/ "https://core.telegram.org") The `url-encode` template function escapes strings. All input characters that are not a-z, A-Z, 0-9, '-', '.', '_' or '\~' are converted to their "URL escaped" version.
*Description:* The `url-encode` template function escapes strings for use as URI path or query parameter segments or form encoded HTTP POST data. All input characters that are not a-z, A-Z, 0-9, '-', '.', '_' or '\~' are converted to their "URL escaped" version.

Available in {{% param "product.abbrev" %}} version 3.18 and later. (In version 3.16-3.17, this template function was called `urlencode`.)

Expand Down