--- layout: default title: Authority URI part Object API --- The Authority part ======= The `League\Uri\Components\Authority` class ease URI authority part creation and manipulation. This object exposes: - the [package common API](/components/2.0/api/), but also provide specific methods to work with a URI authority part.

If the modifications do not change the current object, it is returned as is, otherwise, a new modified object is returned.

If the submitted value is not valid a League\Uri\Exceptions\SyntaxError exception is thrown.

## Instantiation ### Using the default constructor

The default constructor is deprecated starting with version 2.3.0. It should be replaced by one of the several new named constructors.

~~~php submitted string is normalized to be RFC3986 compliant.

### Using a string ~~~php getContent(); //returns 'user:pass@example.com:42' ~~~

if no string is given a instance is returns using the empty string.

### Using Uri components ~~~php getContent(); //returns 'user:pass@example.com:42' ~~~

If you supply your own hash to createFromComponents, you are responsible for providing well parsed components without their URI delimiters.

### Using an URI object The URI must implements League `UriInterface` or PSR-7 `UriInterface`. ~~~php getPort(); //return null; ~~~ ### Using null ~~~php getContent(); //return null; ~~~ Authority validation ------- A `League\Uri\Contracts\UriException` exception is triggered if an invalid Authority value is given. ~~~php $uri = Authority::createFromString(':80'); // throws a League\Uri\Exceptions\SyntaxError // because the URI string is invalid ~~~ Accessing properties ------- The Authority object exposes the following specific methods. ~~~php public function Authority::getUserInfo(void): ?string public function Authority::getHost(void): ?string public function Authority::getPort(void): ?int ~~~ You can access the authority string, its individual parts and components using their respective getter methods. This lead to the following result for a simple HTTP URI: ~~~php $uri = Authority::createFromString("foo:bar@www.example.com:81"); echo $uri->getUserInfo(); //displays "foo:bar" echo $uri->getHost(); //displays "www.example.com" echo $uri->getPort(); //displays 81 as an integer echo $uri; //displays "foo:bar@www.example.com:81" echo json_encode($uri); //displays "foo:bar@www.example.com:81" ~~~ Modifying properties ------- To replace one of the URI component you can use the modifying methods exposed by all URI object. If the modifications do not alter the current object, it is returned as is, otherwise, a new modified object is returned.

Any modification method can trigger a League\Uri\Contracts\UriException exception if the resulting URI is not valid. Just like with the instantiation methods, validition is scheme dependant.

~~~php withUserInfo("foo", "bar") ->withHost("www.example.com") ->withPort(81); echo $uri->getUriComponent(); //displays "//foo:bar@www.example.com:81" ~~~ Normalization ------- Out of the box the package normalizes the URI part according to the non destructive rules of RFC3986. These non destructive rules are: - scheme and host components are lowercased; - the host is converted to its ascii representation using punycode if needed ~~~php $uri = new Uri("www.ExAmPLE.com:80"); echo $uri; //displays www.example.com:80 ~~~

Host conversion depends on the presence of the ext-intl extension. Otherwise the code will trigger a IdnSupportMissing exception