by GµårÐïåñ » Thu Apr 09, 2009 1:31 am
Giorgio, any way we can have each site have a mini policy for cross site requirements. Let me explain:
Say you want to allow devil.com on the site heaven-and-hell.com always BUT you don't want to allow devil.com on any other site that references to it. This way you don't have to choose between temporarily allow or always allow or untrusted, you can make more robust choices?
Is there anyway to do this right now? and if not, would it be something that you can implement in a future release? I find myself in quite a bit of situations where I am willing to allow that site for use with that particular site because I know how its used but NOT for any other site but there is no clean way to do it.
Currently I achieve this on a limited basis using RequestPolicy which has a paired allow policy A->B but not all have access to B just A.
Giorgio, any way we can have each site have a mini policy for cross site requirements. Let me explain:
Say you want to allow [b][i]devil.com[/i][/b] on the site [b][i]heaven-and-hell.com[/i][/b] always BUT you don't want to allow [i][u]devil.com[/u][/i] on any other site that references to it. This way you don't have to choose between temporarily allow or always allow or untrusted, you can make more robust choices?
Is there anyway to do this right now? and if not, would it be something that you can implement in a future release? I find myself in quite a bit of situations where I am willing to allow that site for use with that particular site because I know how its used but NOT for any other site but there is no clean way to do it.
Currently I achieve this on a limited basis using RequestPolicy which has a paired allow policy A->B but not all have access to B just A.