Timeline for Unwanted Sitecore URL
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2019 at 13:04 | history | edited | Vincent Lui | CC BY-SA 4.0 |
added 9 characters in body
|
| Jan 24, 2019 at 13:02 | comment | added | Vincent Lui | If you must, override the item resolver in the pipeline. I will not recommend this approach however as I'm sure by doing so, something else will be broken. Hence my original answer. | |
| Jan 24, 2019 at 9:54 | comment | added | samridhi sachdeva | so what's the way to restrict these URLs on public site ? | |
| Jan 24, 2019 at 9:48 | comment | added | Mark Cassidy♦ | There is no misconfiguration though. Since Sitecore 5, it has been possible to use hostname/sitecore/content/home to reach the home node. It's by design. | |
| Jan 24, 2019 at 5:49 | comment | added | samridhi sachdeva | ya I don't want to go with redirects option, also I don't have the Robots.txt in my website. | |
| Jan 24, 2019 at 5:01 | comment | added | Peter Procházka | You are trying to find solution for the current situation not the root cause of the problem. Redirection will not help here. This must be a problem of misconfiguration of site in Sitecore | |
| Jan 24, 2019 at 2:13 | history | answered | Vincent Lui | CC BY-SA 4.0 |