We've got a question about the accessPolicy for Handlers in web.config. Default it's this, when installing umbraco:
handlers accessPolicy="Read, Write, Script, Execute"
This creates errors/warnings in IIS. And a reccomendation: "IIS: Grant a handler execute/script or write permissions, but not both"
Can someone please tell me if umbraco will still function properly if we change the accessPolicy to "Read, Script" or "Excecute, Script". And what would be the best solution then?
Is there a good reason for default, it's wrongfully configured?
In hindsight, I think I hadn't quite configured the server properly in the first instance (I'd missed some options from Roles & Features > Web Server (IIS) > Web Server > Application Development), but this got me moving anyway.
accessPolicy for Handlers in web.config file, Read, Write, Script, Execute
Hi,
We've got a question about the accessPolicy for Handlers in web.config. Default it's this, when installing umbraco: handlers accessPolicy="Read, Write, Script, Execute"
This creates errors/warnings in IIS. And a reccomendation: "IIS: Grant a handler execute/script or write permissions, but not both"
https://technet.microsoft.com/en-us/library/dd391910(v=ws.10).aspx
Can someone please tell me if umbraco will still function properly if we change the accessPolicy to "Read, Script" or "Excecute, Script". And what would be the best solution then?
Is there a good reason for default, it's wrongfully configured?
Greeting, Remko
Nobody got this problem?
Yep, I got this. Fixed it with the reply from Overflew here - http://stackoverflow.com/questions/9794985/iis-this-configuration-section-cannot-be-used-at-this-path-configuration-lock
In hindsight, I think I hadn't quite configured the server properly in the first instance (I'd missed some options from Roles & Features > Web Server (IIS) > Web Server > Application Development), but this got me moving anyway.
is working on a reply...