compared with
Current by Dolf Schimmel (Freeaqingme)
on Feb 11, 2011 13:00.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (17)

View Page History
<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{zone-template-instance:ZFPROP:Proposal Zone Template}

* Host part address types
const HOST_IPV4 = 1; // IPv4 address
const HOST_IPV6 = 2; // IPv6 address
const HOST_IPVF = 4; // IPvx (future) address
const HOST_IPVANY = 7; // Any IP address
const HOST_DNSNAME = 8; // DNS name
const HOST_DNSORIPV4 = 9; // DNS or IPv4
const HOST_REGNAME = 16; // Registered name
const HOST_ALL = 31; // Any address type

* Character classes defined in RFC-3986
static public function validateUserInfo($userInfo);

* Validate the host part
* Users may control which host types to allow by passing a second parameter
* with a bitmask of HOST_* constants which are allowed. If not specified,
* This allows different host representations, including IPv4 addresses, all address types will be allowed.
* Note that the generic URI syntax allows different host representations,
* including IPv4 addresses, IPv6 addresses and future IP address formats
* IPv6 addresses enclosed in square brackets, and registered names which may be DNS names
* may be DNS names or even more complex names. This is different (and is much more loose)
* more loose) from what is commonly accepted as valid HTTP URLs for example.
* example.
* @param string $host
* @todo Users should be able to control which host types are allowed
* @param string $host
* @param integer $allowed bitmask of allowed host types
* @return boolean
static public function validateHost($host, $allowed = self::HOST_ALL);