Class HTMLPurifier_URIFilter
Chainable filters for custom URI processing.
These filters can perform custom actions on a URI filter object, including transformation or blacklisting. A filter named Foo must have a corresponding configuration directive %URI.Foo, unless always_load is specified to be true.
The following contexts may be available while URIFilters are being
processed:
- EmbeddedURI: true if URI is an embedded resource that will be loaded
automatically on page load - CurrentToken: a reference to the token that is
currently being processed - CurrentAttr: the name of the attribute that is
currently being processed - CurrentCSSProperty: the name of the CSS property
that is currently being processed (if applicable)
Direct known subclasses
HTMLPurifier_URIFilter_DisableExternal, HTMLPurifier_URIFilter_DisableResources, HTMLPurifier_URIFilter_HostBlacklist, HTMLPurifier_URIFilter_MakeAbsolute, HTMLPurifier_URIFilter_Munge, HTMLPurifier_URIFilter_SafeIframeIndirect known subclasses
HTMLPurifier_URIFilter_DisableExternalResourcesWarning: This filter is called before scheme object validation occurs. Make sure, if you require a specific scheme object, you you check that it exists. This allows filters to convert proprietary URI schemes into regular ones.
Located at x2engine/framework/vendors/htmlpurifier/HTMLPurifier.standalone.php
public
boolean
|
#
prepare(
Performs initialization for the filter. If the filter returns false, this means that it shouldn't be considered active. |
abstract public
boolean
|
#
filter(
Filter a URI object |
public
mixed
|
$name |
|
#
Unique identifier of filter. |
public
boolean
|
$post | false |
#
True if this filter should be run after scheme validation. |
public
boolean
|
$always_load | false |
#
True if this filter should always be loaded. This permits a filter to be named Foo without the corresponding %URI.Foo directive existing. |