Url¶
Validates that a value is a valid URL string.
Applies to | property or method |
Options | |
Class | Url |
Validator | UrlValidator |
Basic Usage¶
- Annotations
1 2 3 4 5 6 7 8 9 10 11 12
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; class Author { /** * @Assert\Url */ protected $bioUrl; }
- YAML
1 2 3 4 5
# config/validator/validation.yaml App\Entity\Author: properties: bioUrl: - Url: ~
- XML
1 2 3 4 5 6 7 8 9 10 11 12
<!-- config/validator/validation.xml --> <?xml version="1.0" encoding="UTF-8" ?> <constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping https://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd"> <class name="App\Entity\Author"> <property name="bioUrl"> <constraint name="Url"/> </property> </class> </constraint-mapping>
- PHP
1 2 3 4 5 6 7 8 9 10 11 12 13
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; use Symfony\Component\Validator\Mapping\ClassMetadata; class Author { public static function loadValidatorMetadata(ClassMetadata $metadata) { $metadata->addPropertyConstraint('bioUrl', new Assert\Url()); } }
This constraint doesn’t check that the host of the given URL really exists,
because the information of the DNS records is not reliable. Use the
checkdnsrr
PHP function if you still want to check that.
注釈
As with most of the other constraints, null
and empty strings are
considered valid values. This is to allow them to be optional values.
If the value is mandatory, a common solution is to combine this constraint
with NotBlank.
Options¶
groups
¶
type: array
| string
It defines the validation group or groups this constraint belongs to. Read more about validation groups.
message¶
type: string
default: This value is not a valid URL.
This message is shown if the URL is invalid.
You can use the following parameters in this message:
Parameter | Description |
---|---|
{{ value }} |
The current (invalid) value |
- Annotations
1 2 3 4 5 6 7 8 9 10 11 12 13 14
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; class Author { /** * @Assert\Url( * message = "The url '{{ value }}' is not a valid url", * ) */ protected $bioUrl; }
- YAML
1 2 3 4 5 6
# config/validator/validation.yaml App\Entity\Author: properties: bioUrl: - Url: message: The url "{{ value }}" is not a valid url.
- XML
1 2 3 4 5 6 7 8 9 10 11 12 13 14
<!-- config/validator/validation.xml --> <?xml version="1.0" encoding="UTF-8" ?> <constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping https://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd"> <class name="App\Entity\Author"> <property name="bioUrl"> <constraint name="Url"> <option name="message">The url "{{ value }}" is not a valid url.</option> </constraint> </property> </class> </constraint-mapping>
- PHP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; use Symfony\Component\Validator\Mapping\ClassMetadata; class Author { public static function loadValidatorMetadata(ClassMetadata $metadata) { $metadata->addPropertyConstraint('bioUrl', new Assert\Url([ 'message' => 'The url "{{ value }}" is not a valid url.', ])); } }
normalizer¶
type: a PHP callable default: null
This option allows to define the PHP callable applied to the given value before checking if it is valid.
For example, you may want to pass the 'trim'
string to apply the
trim
PHP function in order to ignore leading and trailing
whitespace during validation.
payload
¶
type: mixed
default: null
This option can be used to attach arbitrary domain-specific data to a constraint. The configured payload is not used by the Validator component, but its processing is completely up to you.
For example, you may want to use several error levels to present failed constraints differently in the front-end depending on the severity of the error.
protocols¶
type: array
default: ['http', 'https']
The protocols considered to be valid for the URL. For example, if you also consider
the ftp://
type URLs to be valid, redefine the protocols
array, listing
http
, https
, and also ftp
.
- Annotations
1 2 3 4 5 6 7 8 9 10 11 12 13 14
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; class Author { /** * @Assert\Url( * protocols = {"http", "https", "ftp"} * ) */ protected $bioUrl; }
- YAML
1 2 3 4 5
# config/validator/validation.yaml App\Entity\Author: properties: bioUrl: - Url: { protocols: [http, https, ftp] }
- XML
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
<!-- config/validator/validation.xml --> <?xml version="1.0" encoding="UTF-8" ?> <constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping https://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd"> <class name="App\Entity\Author"> <property name="bioUrl"> <constraint name="Url"> <option name="protocols"> <value>http</value> <value>https</value> <value>ftp</value> </option> </constraint> </property> </class> </constraint-mapping>
- PHP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; use Symfony\Component\Validator\Mapping\ClassMetadata; class Author { public static function loadValidatorMetadata(ClassMetadata $metadata) { $metadata->addPropertyConstraint('bioUrl', new Assert\Url([ 'protocols' => ['http', 'https', 'ftp'], ])); } }
relativeProtocol¶
type: boolean
default: false
If true
, the protocol is considered optional when validating the syntax of
the given URL. This means that both http://
and https://
are valid but
also relative URLs that contain no protocol (e.g. //example.com
).
- Annotations
1 2 3 4 5 6 7 8 9 10 11 12 13 14
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; class Author { /** * @Assert\Url( * relativeProtocol = true * ) */ protected $bioUrl; }
- YAML
1 2 3 4 5
# config/validator/validation.yaml App\Entity\Author: properties: bioUrl: - Url: { relativeProtocol: true }
- XML
1 2 3 4 5 6 7 8 9 10 11 12 13 14
<!-- config/validator/validation.xml --> <?xml version="1.0" encoding="UTF-8" ?> <constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping https://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd"> <class name="App\Entity\Author"> <property name="bioUrl"> <constraint name="Url"> <option name="relativeProtocol">true</option> </constraint> </property> </class> </constraint-mapping>
- PHP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
// src/Entity/Author.php namespace App\Entity; use Symfony\Component\Validator\Constraints as Assert; use Symfony\Component\Validator\Mapping\ClassMetadata; class Author { public static function loadValidatorMetadata(ClassMetadata $metadata) { $metadata->addPropertyConstraint('bioUrl', new Assert\Url([ 'relativeProtocol' => true, ])); } }