Best Practice for changing the backoffice url to something other than /umbraco/
In searching for an answer to this question, I've found various stale and slightly ambiguous postings going back a number of years. I'm interested in the answer circa 2014, for umbraco 7. I understand that some of the approaches documented in the past present the risk of not working with packages that hard code urls. Hopefully that's not an issue with V7 as packages are going through the upgrade process and package developers know of this issue.
Is the reason for changing umbraco url to obfuscate admin layer? We used to do this however now we just in iis tie down the umbraco folder to specific ip addresses.
Best Practice for changing the backoffice url to something other than /umbraco/
In searching for an answer to this question, I've found various stale and slightly ambiguous postings going back a number of years. I'm interested in the answer circa 2014, for umbraco 7. I understand that some of the approaches documented in the past present the risk of not working with packages that hard code urls. Hopefully that's not an issue with V7 as packages are going through the upgrade process and package developers know of this issue.
Any help would be greatly appreciated..
Stewart,
Is the reason for changing umbraco url to obfuscate admin layer? We used to do this however now we just in iis tie down the umbraco folder to specific ip addresses.
Regards
Ismail
Yes, that is the reason. I'm aware of the ip address approach - I was just wondering if there is any other good option.
Thanks
Stewart
is working on a reply...