From 1a0e99b282b98fe370ae5feb59034a05d6048e39 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Tue, 25 Jul 2023 12:56:35 -0300 Subject: [PATCH] Changed texts to be good and bad examples "specific-characters-URL" --- .../rule.md | 21 ++++++++++++------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/rules/avoid-using-specific-characters-in-friendly-url/rule.md b/rules/avoid-using-specific-characters-in-friendly-url/rule.md index b15ce9f1bfd..6cc974a8889 100644 --- a/rules/avoid-using-specific-characters-in-friendly-url/rule.md +++ b/rules/avoid-using-specific-characters-in-friendly-url/rule.md @@ -26,11 +26,16 @@ When adding a friendly URL, please avoid using specific characters like `+ : # & Some characters are reserved characters, which may not be supported by some features, based on our experience, “+" is not supported in “canonical" to redirect from **http** to **https**. -For example: - -`http://ssw.com.au/rules/when-to-use-+1` -will throw a 404 error rather than redirecting to -`https://ssw.com.au/rules/when-to-use-+1`. - -It would work fine if the URL doesn't include “+", like: -`http://ssw.com.au/rules/when-to-use-plus-1`. +::: greybox +http://ssw.com.au/rules/when-to-use-+1 +::: +::: bad +Figure: Bad example - This URL will throw a 404 error rather than redirecting to https:// +::: + +::: greybox +http://ssw.com.au/rules/when-to-use-plus-1 +::: +::: good +Figure: Good example - Redirect works fine if the URL doesn't include “+" +:::