|  | Home · All Classes · Modules

# QWebSecurityOrigin Class Reference
[QtWebKit module]

The QWebSecurityOrigin class defines a security boundary for web sites. More...

### Methods

- __init__ (self, QWebSecurityOrigin)
- int databaseQuota (self)
- QList<QWebDatabase>list-of-QWebDatabase databases (self)
- int databaseUsage (self)
- QStringQString host (self)
- int port (self)
- QStringQString scheme (self)
- setDatabaseQuota (self, int)

### Static Methods

- addLocalScheme (QStringQString)
- QList<QWebSecurityOrigin>list-of-QWebSecurityOrigin allOrigins ()
- QStringListQStringList localSchemes ()
- removeLocalScheme (QStringQString)

## Detailed Description

The QWebSecurityOrigin class defines a security boundary for web sites.

QWebSecurityOrigin provides access to the security domains defined by web sites. An origin consists of a host name, a scheme, and a port number. Web sites with the same security origin can access each other's resources for client-side scripting or databases.

For example the site `http://www.example.com/my/page.html` is allowed to share the same database as `http://www.example.com/my/overview.html`, or access each other's documents when used in HTML frame sets and JavaScript. At the same time it prevents `http://www.malicious.com/evil.html` from accessing `http://www.example.com/`'s resources, because they are of a different security origin.

Call QWebFrame.securityOrigin() to get the QWebSecurityOrigin for a frame in a web page, and use host(), scheme() and port() to identify the security origin.

Use databases() to access the databases defined within a security origin. The disk usage of the origin's databases can be limited with setDatabaseQuota(). databaseQuota() and databaseUsage() report the current limit as well as the current usage.

For more information refer to the "Same origin policy" Wikipedia Article.

See also QWebFrame.securityOrigin().

## Method Documentation

### QWebSecurityOrigin.__init__ (self, QWebSecurityOrigin)

Constructs a security origin from other.

### QWebSecurityOrigin.addLocalScheme (QStringQString)

Adds the given scheme to the list of schemes that are considered equivalent to the `file`: scheme. They are not subject to cross domain restrictions.

This function was introduced in Qt 4.6.

### QList<QWebSecurityOrigin>list-of-QWebSecurityOrigin QWebSecurityOrigin.allOrigins ()

Returns a list of all security origins with a database quota defined.

### int QWebSecurityOrigin.databaseQuota (self)

Returns the quota for the databases in the security origin.

See also setDatabaseQuota().

### QList<QWebDatabase>list-of-QWebDatabase QWebSecurityOrigin.databases (self)

Returns a list of all databases defined in the security origin.

### int QWebSecurityOrigin.databaseUsage (self)

Returns the number of bytes all databases in the security origin use on the disk.

### QStringQString QWebSecurityOrigin.host (self)

Returns the host name defining the security origin.

### QStringListQStringList QWebSecurityOrigin.localSchemes ()

Returns a list of all the schemes that were set by the application as local schemes,

This function was introduced in Qt 4.6.

See also addLocalScheme() and removeLocalScheme().

### int QWebSecurityOrigin.port (self)

Returns the port number defining the security origin.

### QWebSecurityOrigin.removeLocalScheme (QStringQString)

Removes the given scheme from the list of local schemes.

This function was introduced in Qt 4.6.

See also addLocalScheme().

### QStringQString QWebSecurityOrigin.scheme (self)

Returns the scheme defining the security origin.

### QWebSecurityOrigin.setDatabaseQuota (self, int)

Sets the quota for the databases in the security origin to quota bytes.

If the quota is set to a value less than the current usage, the quota will remain and no data will be purged to meet the new quota. However, no new data can be added to databases in this origin.

See also databaseQuota().