43
edits
Specifications/Cross Domain Access Policies: Difference between revisions
Jump to navigation
Jump to search
Specifications/Cross Domain Access Policies (view source)
Revision as of 15:53, 23 May 2005
, 23 May 2005added IDN
m (Clean up and improve clarity (says me ;) )) |
(added IDN) |
||
| Line 32: | Line 32: | ||
=== Whitelisting === | === Whitelisting === | ||
The policy file works like a whitelist. It lists which outside domains have access to web-services and what types of services they may consume. The '''allow''' element is used for this, and the domain is specified in it's '''from''' attribute. Full domains may be used, such as <tt><nowiki>www.foo.com</nowiki></tt>, or wildcarded ones such as <tt><nowiki>*.foo.com</nowiki></tt>, or even just <tt><nowiki>*</nowiki></tt> to allow any domain. If no '''from''' attribute is set, then any domain is allowed. | The policy file works like a whitelist. It lists which outside domains have access to web-services and what types of services they may consume. The '''allow''' element is used for this, and the domain is specified in it's '''from''' attribute. Full domains may be used, such as <tt><nowiki>www.foo.com</nowiki></tt>, or wildcarded ones such as <tt><nowiki>*.foo.com</nowiki></tt>, or even just <tt><nowiki>*</nowiki></tt> to allow any domain. If no '''from''' attribute is set, then any domain is allowed. If the implementor is [http://www.ietf.org/html.charters/idn-charter.html IDN] aware, then the '''from''' attribute should be IDN aware as well. | ||
=== Types of Services === | === Types of Services === | ||