Because of this, I've set forcewwwUrls="True" on my local environment, and committed the file to git. This means, that the rule now applies to all environments, but since the *.s1.umbraco.io hostnames does not support www, I get an error on all environments (other than live, which is using the live domain which does support www). I can disable the force www on the other environments, but this is reset on every commit (again because of this).
Could you negate the "*.s1.umbraco.io" urls from the rewrite rule?
Will add that to the list, but currently main prio is to get all packages working on V8. What you could do is use the ignore option and add a rewrite rule in IIS?
forcewwwUrls interferes with Umbraco Cloud environments
Because of this, I've set
forcewwwUrls="True"on my local environment, and committed the file to git. This means, that the rule now applies to all environments, but since the *.s1.umbraco.io hostnames does not support www, I get an error on all environments (other than live, which is using the live domain which does support www). I can disable the force www on the other environments, but this is reset on every commit (again because of this).Could you negate the "*.s1.umbraco.io" urls from the rewrite rule?
Hi Ole,
Will add that to the list, but currently main prio is to get all packages working on V8. What you could do is use the ignore option and add a rewrite rule in IIS?
Best,
Richard
That's how I used to do it. But I wanted to use Seochecker for as much as possible. But will do that until a fix is ready, np.
is working on a reply...