Updated Troubleshooting (markdown)

master
Chris Caron 2019-04-27 23:53:39 -04:00
parent 08be657b04
commit 963c9ad2eb
1 changed files with 1 additions and 1 deletions

@ -30,4 +30,4 @@ Below is a chart of special characters and the value you should set them:
| **@** | **%40** | The at symbol is what divides the user and/or password from hostname in a URL. if your username and/or password contains an '@' symbol, it can cause the url parser to get confused.
| **+** | **%2B** | By default a addition/plus symbol **(+)** is interpreted as a _space_ when specified in the URL. It must be escaped if you actually want the character to be represented as a **+**.
| **,** | **%2C** | A comma only needs to be escaped in _extremely rare circumstances_ where one exists at the very end of a specific URL that has been chained with others using a comma. [See PR#104](https://github.com/caronc/apprise/pull/104) for more details as to why you _may_ need this.
| **:** | **%3A** | A colon will never need to be escaped unless it is found as part of a user/pass combination. Hence in a url `http://user:pass@host` you can see that a colon is already used to delimit the username from the password. Thus if your _{user}_ actually has a colon in it, it can confuse the parser into thinking your at the start of your password. This is a very rare case where a colon may need to be escaped.
| **:** | **%3A** | A colon will never need to be escaped unless it is found as part of a user/pass combination. Hence in a url `http://user:pass@host` you can see that a colon is already used to separate the _username_ from the _password_. Thus if your _{user}_ actually has a colon in it, it can confuse the parser into treating what follows as a password (and not the remaining of your username). This is a very rare case as most systems don't allow a colon in a username field.