The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The NBAR Web-based Custom Protocols feature provides the mechanism to define custom protocols to match based on HTTP URL and/or host name.
The HTTP URL and the Host name defined for custom protocol match should be unique. The length of the protocol name should be at least 4 characters long and the prefix of the protocol name should be different from the prefixes of any other protocol name.
The NBAR Web-based Custom Protocols feature provides the mechanism to define custom protocols to match the traffic based on HTTP URL and/or host name.
All 120 custom protocols can be defined to match based on HTTP URL and/or host name. While matching web-based custom protocols, the custom protocol that has both HTTP URL and the host name defined has the highest priority, followed by HTTP URL as the second priority, and then followed by Host name as the last priority. Matching a web-based sub-protocol has higher priority than matching any type of web-based custom protocol, for example the match protocol http url http-url command has a higher priority than a custom priority with the same URL configuration.
How to Define NBAR Web-based Custom Protocols Match
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
| Step 3 |
ip nbar custom custom-protocol-name http { host host-name | url http-url [ host host-name]} [ id selector-id] Example: |
Defines web-based custom protocol match.
|
||
| Step 4 |
end Example: |
(Optional) Exits global configuration mode. |
Configuration Examples for NBAR Web-based Custom Protocols
The following example displays how to match a custom protocol based on http url:
Router> enable
Router# configure terminal
Router(config)# ip nbar custom app_sales1 http url www.example.com
The following example displays how to match a custom protocol that contains the string 'example' as a part of host name:
Router> enable
Router# configure terminal
Router(config)# ip nbar custom app_sales1 http host *example*|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
|
|
Custom Protocols |
Creating a Custom Protocol module |
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
NBAR Web-based Custom Protocols Scalability |
15.4(3)T 15.5(1)T |
The NBAR Web-based Custom Protocols Scalability feature enables defining custom protocols match based on http host name and/or url. The following command was introduced or modified: ip nbar custom . |
Feedback