Difference between revisions of "Same-origin policy"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 19: | Line 19: | ||
== See also == | == See also == | ||
| + | * [[Ajax (programing)]] | ||
* [[Document object model]] | * [[Document object model]] | ||
* [[Web application]] | * [[Web application]] | ||
* [[Web browser]] | * [[Web browser]] | ||
| + | * [[Web service]] | ||
== External links == | == External links == | ||
* [http://en.wikipedia.org/wiki/Same-origin_policy Same-origin policy] @ Wikipedia | * [http://en.wikipedia.org/wiki/Same-origin_policy Same-origin policy] @ Wikipedia | ||
Revision as of 07:16, 31 August 2015
In computing, the same-origin policy is an important concept in the web application security model.
Contents
Description
Under the policy, a web browser permits scripts contained in a first web page to access data in a second web page, but only if both web pages have the same origin.
An origin is defined as a combination of URI scheme, hostname, and port number.
This policy prevents a malicious script on one page from obtaining access to sensitive data on another web page through that page's Document Object Model.
Cookies
This mechanism bears a particular significance for modern web applications that extensively depend on HTTP cookies to maintain authenticated user sessions, as servers act based on the HTTP cookie information to reveal sensitive information or take state-changing actions.
A strict separation between content provided by unrelated sites must be maintained on the client side to prevent the loss of data confidentiality or integrity.
See also
External links
- Same-origin policy @ Wikipedia
