From 562bde1a1c2758d8324e99160c3b0f42e972c7ae Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Wed, 6 Jul 2022 13:21:12 -0400 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index ebc8a55..4918c4b 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -161,7 +161,7 @@ The thing with Apprise is it doesn't know what you're feeding it (the format the ## Apprise URLs on Command Line Do Not Behave Correctly If you are passing a URL on the Command Line Interface (CLI) of your Linux/Windows/Mac shell, it is important that you surround the URL with "quotes". URL's leverage the `&` character which delimits one parameter from another (e.g. `schema://config?parm=value&parm2=value`). -The problem is that `&` characters are also interpreted by the CLI. The `&` causes the shell to execute everything defined before them into a background process. +The problem is that `&` characters are also interpreted by the CLI. The `&` causes the shell to execute everything defined before them into a background process. As a result, you would actually loose and not register any parameters beyond the first. ```bash # Here is an example of a problematic Apprise URL without "quotes": apprise -vvv -b "Test Email" \ @@ -173,7 +173,9 @@ apprise -vvv -b "Test Email" \ # | # This launches the first part into Apprise as a # background task depending on the CLI handles the -# entries specified after here very differently +# entries specified after here very differently. Hence +# only "mailtos://user:pass@example.com?mode=ssl" was +# loaded into Apprise with respect to this example. # # This is VERY likely NOT what you expect/want to happen.