Using a custom domain for accessing umbraco

By default, content editors will be editing their content by appending umbraco to their domain. Sometimes you might not want your content editor to use that method and would like them to use an alternative URL. This could be for a few reasons…

Below is an example of how to do this. We match the URL for Umbraco and then perform a redirect to our not found page if it doesn’t match our pattern. Note this part: (?!Surface) - this is important as it means that AJAX calls using Surface controllers still work.

Therefore, when editing the Umbraco site and assuming will only have an SSL certificate for Umbraco, a content editor will use:

https://admin.example.com/umbraco/

Whereas, the site will be visible at:

http://www.example.com/

If you have done something similar or have alternatives that you use, then please feel free to leave a comment!


I am on Twitter as mozzy16, if you liked this post please feel free to share it with your followers.