custom-objects
Syntax
custom-objects {
custom-url-category object-name {
value [value];
}
custom-message {
name message-name;
type redirect-url | user-message;
content redirect-url by user| user-message by user;
}
filename-extension object-name {
value [value];
}
mime-pattern object-name {
value [value];
}
protocol-command object-name {
value [value];
}
url-pattern object-name {
value [value];
}
}
Hierarchy Level
[edit security utm] [edit security utm default-configuration] [edit logical-systems logical-system-name security utm] [edit tenants tenant-name security utm]
Description
Configure custom objects before configuring Content Security feature-profile features.
Custom category does not take precedence over predefined categories when it has the same name as one of the predefined categories. We do not recommend having a custom category name be the same as the predefined category name.
Starting from Junos OS Release 17.4R1, support for custom category configuration is available for EWF, local, and Websense redirect profiles.
Options
The statements are explained separately. See CLI Explorer.
Required Privilege Level
security—To view this statement in the configuration.
security-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy
level introduced in Junos OS Release 18.2R1.
Support for configuration in logical systems introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1.