Our client requires that their production backoffice to Umbraco to be run off a seperate sub domain from the front end of their production site so to achive this we are using the following rule:
This works fine in that if a person types in http://domain.com/umbraco they get a 403 and if a person types in http://sub.domain.com/umbraco they get access to the back end. However when we now try to courier files from our development site to our production site we get a courier error.
Does anybody know what I need to ammend in my regex to allow courier to deploy content?
I have tried to ammend the courier config to reference the sub.domain.com site but it still failed
I've had a similar problem on Umbraco Cloud, where the problem was that the UmbracoDeploy / Courier requests went to /App_Plugins/* which wasn't handled in the rewrites.
I can't really tell if this is related... can you see the requested path(s) that get rejected?
Courier and URL rewrite
Our client requires that their production backoffice to Umbraco to be run off a seperate sub domain from the front end of their production site so to achive this we are using the following rule:
This works fine in that if a person types in http://domain.com/umbraco they get a 403 and if a person types in http://sub.domain.com/umbraco they get access to the back end. However when we now try to courier files from our development site to our production site we get a courier error.
Does anybody know what I need to ammend in my regex to allow courier to deploy content?
I have tried to ammend the courier config to reference the sub.domain.com site but it still failed
Many thanks
Hi David,
I've had a similar problem on Umbraco Cloud, where the problem was that the UmbracoDeploy / Courier requests went to
/App_Plugins/*
which wasn't handled in the rewrites.I can't really tell if this is related... can you see the requested path(s) that get rejected?
/Chriztian
is working on a reply...