We have the following URL "/blog/tags/ab%26c%20lorem%20ipsum" reported in the Inbound link errors. We redirect it to the /blogs page. However, the configuration is not working. Visiting the URL results into a Bad Request. To eliminate Articulate as causing the issue, we created a new redirect for "/ab%26c%20lorem%20ipsum" but that one results to a Bad Request as well. How can we fix that link?
Thanks for your reply. The site is on 2.0.1. We removed the inbound link error, visited the same URL just to check if the plugin will capture it and it did. The link, after being pointed to a valid content, still resulted into a Bad Result.
Hi Richard, I just updated to 2.2.0. I removed the redirect from the Redirect manager. I then visited the site but the URL is no longer recorded in the Inbound link errors. I visited the URL several times but the plugin cannot capture it anymore.
Great to see it doesn't get logged anymore. The thing is that it will break anyway on an Umbraco website. The url /blog/tags/ab%26c%20lorem%20ipsum contains & and that will always throw a 500 error. I don't think Google won't index this url as well?
URLs with %26 are not redirecting
Hello,
We have the following URL "/blog/tags/ab%26c%20lorem%20ipsum" reported in the Inbound link errors. We redirect it to the /blogs page. However, the configuration is not working. Visiting the URL results into a Bad Request. To eliminate Articulate as causing the issue, we created a new redirect for "/ab%26c%20lorem%20ipsum" but that one results to a Bad Request as well. How can we fix that link?
Hi Von,
When testing this the url already results in before logging"A potentially dangerous Request.Path value was detected from the client (&)."
Nothing is logged, was this an older version that was creating the inbound link error entry?
Best,
Richard
Hi Richard,
Thanks for your reply. The site is on 2.0.1. We removed the inbound link error, visited the same URL just to check if the plugin will capture it and it did. The link, after being pointed to a valid content, still resulted into a Bad Result.
How should we configure it?
Best to update to the latest version as well. A minor issue with redirects was solved in that release.
Best,
Richard
Hi Richard, I just updated to 2.2.0. I removed the redirect from the Redirect manager. I then visited the site but the URL is no longer recorded in the Inbound link errors. I visited the URL several times but the plugin cannot capture it anymore.
Hi Von,
Great to see it doesn't get logged anymore. The thing is that it will break anyway on an Umbraco website. The url /blog/tags/ab%26c%20lorem%20ipsum contains & and that will always throw a 500 error. I don't think Google won't index this url as well?
I wouldn't worry to much about this url.
Best,
Richard
Make sense. Thanks for your input Richard!
is working on a reply...