No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NETCONF YANG API Reference

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

NETCONF YANG API Reference
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
URL Filtering

URL Filtering

Data Model

The data model file matching the URL filtering profile is huawei-url-filter.yang.

Table 3-1319 URL filtering data model

Object

Description

url-filter

Indicates that the operation request object is URL filtering profiles. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys

Indicates that the operation request object is the system. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/name

Indicates the name of a system, which is in string format.

url-filter/vsys/profiles

Indicates that the operation request object is all URL filtering profiles. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/profiles/profile

Indicates that the operation request object is the current URL filtering profile. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/profiles/profile/name

Indicates the name of a URL filtering profile. The value is a string of case-sensitive characters.

  • If the name does not contain spaces, the value is a string of 1 to 32 characters.
  • If the name contains spaces, the value is a string of 3 to 34 characters, and the name must be enclosed with double quotation marks (""), for example, "user for test". The name cannot contain question marks (?), commas (,), double quotation marks ("), and hyphens (-).

url-filter/vsys/profiles/profile/description

Description of the URL filtering profile. The value is a string of 1 to 128 case-sensitive characters including spaces.

url-filter/vsys/profiles/profile/default-action

Default action in the URL filtering profile. Three options are available: allow, alert, and block.

url-filter/vsys/profiles/profile/whitelist

Indicates that the operation request object is URL filtering whitelist. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/whitelist/match-rule

Indicates that the operation request object is the current matching rule. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/whitelist/match-rule/match-scope

Indicates the scope of the matching rule. The value is an enumerated string. Currently, the value can only be url or host.

url-filter/vsys/profiles/profile/whitelist/match-rule/match-type

Indicates the match type of the matching rule. The value is an enumerated string. Currently, the value can be prefix, suffix, fuzzy, and exact.

The following part describes the four match types:

1. prefix:

Definition:

The rule matches all URLs starting with the specified string.

Item:

www.example*

Example:

Match all URLs starting with www.example. Example:

www.example.com

www.example.com/solutions.do

2. suffix:

Definition:

The rule matches all URLs ending with the specified string.

Item:

*aspx

Example:

Match all URLs ending with aspx. Example:

www.example.com/news/solutions.aspx

www.example.com/it/price.aspx

10.1.1.1/sports/abc.aspx

3. fuzzy:

Definition:

The rule matches all URLs containing the specified string.

Item:

*sport*

Example:

Match all URLs containing sport. Example:

sports.example.com/news/solutions.aspx

sports.example.com/it/

10.1.1.1/sports/

4. exact:

Definition:

Check whether a URL matches the specified string. If not, remove the last-level directory from the URL and match the URL with the string. If still not matched, remove the last-level directory from the URL and match the URL with the specified string. The process repeats until the URL contains only the domain name.

Item:

www.example.com

Example:

The following URLs can match the rule:

www.example.com.

www.example.com

www.example.com/news

www.example.com/news/en/

The following URLs do not match the rule:

www.example.com.cn/news

www.example.org/news/www.example.com

url-filter/vsys/profiles/profile/whitelist/match-rule/value

1. If the value is host:

The value is a string of 4 to 512 characters and cannot contain slashes (/), backslashes (\), number signs (#), double quotation marks ("), question marks (?), or spaces.

* indicates a wildcard, which can appear at the beginning or end of a domain name. If * is in the middle of a string, it is only a common character, not a wildcard. For example, if a domain name is set to **abc or *a*bc, * at the beginning is a wildcard, and * in the middle is a common character.

  • If the domain name does not contain wildcards, it must contain at least four consecutive characters, for example, abcd.
  • If the domain name contains wildcards, it must contain at least three consecutive characters, for example, *abc, *abc*, **ab, and *a*b.

2. If the value is url:

The value is a string. If the entered URL does not contain spaces or question marks (?), the length after pre-processing ranges from 4 to 512 characters. If the URL contains spaces or question marks (?) (the URL cannot end with a question mark), use a pair of double quotation marks (") to enclose the URL. The length after pre-processing ranges from 6 to 514 characters. The pre-processing means that the system removes the prefix http:// from the string.

If the URL contains double quotation marks ("), replace them with escape characters %22. For example, if the URL is www.example.com/abc/def?"gh, enter www.example.com/abc/def?%22gh instead.

* indicates a wildcard, which can appear at the beginning or end of a URL. If * is in the middle of a string, it is only a common character, not a wildcard. For example, if a URL is set to **abc or *a*bc, * at the beginning is a wildcard, and * in the middle is a common character.

  • If the URL does not contain wildcards, it must contain at least four consecutive characters, for example, abcd.
  • If the URL contains wildcards, it must contain at least three consecutive characters, for example, *abc, *abc*, **ab, and *a*b.

url-filter/vsys/profiles/profile/blacklist

Indicates that the operation request object is URL filtering blacklist. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/blacklist/match-rule

Indicates that the operation request object is the current matching rule. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/blacklist/match-rule/match-scope

See: url-filter/vsys/profiles/profile/whitelist/match-rule/match-scope.

url-filter/vsys/profiles/profile/blacklist/match-rule/match-type

See: url-filter/vsys/profiles/profile/whitelist/match-rule/match-type.

url-filter/vsys/profiles/profile/blacklist/match-rule/value

See: url-filter/vsys/profiles/profile/whitelist/match-rule/value.

url-filter/vsys/profiles/profile/category

Indicates that the operation request object is the category. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/category/action-mode

Action mode of a URL category.

  • The value strict indicates a strict category action mode.
  • The value loose indicates a loose category action mode.

url-filter/vsys/profiles/profile/category/user-defined

User-defined category of a URL category. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/category/user-defined/all-category

All user-defined category actions of the URL category. Three options are available: allow, alert, and block.

NOTE:

The northbound mechanism of this node is faulty. You are advised to perform this operation on all single user-defined category nodes.

url-filter/vsys/profiles/profile/category/user-defined/category

Action of a single user-defined category. It contains only subnodes and has no data significance.

url-filter/vsys/profiles/profile/category/user-defined/category/name

Name of a user-defined category. The length is 1 to 32 characters. If the name contains spaces, it must be enclosed with double quotation marks (""), for example, "user for test".

url-filter/vsys/profiles/profile/category/user-defined/category/action

Action of a user-defined category. Three options are available: allow, alert, and block.

url-filter/vsys/profiles/profile/category/pre-defined

Pre-defined category of a URL category.

url-filter/vsys/profiles/profile/category/pre-defined/level

Control level of all pre-defined URL categories of a URL category.

  • If the value is high, it indicates that the control level of the pre-defined category is high.
  • If the value is medium, it indicates that the control level of the pre-defined category is medium.
  • If the value is low, it indicates that the control level of the pre-defined category is low.
NOTE:

The northbound mechanism of this node is faulty. You are advised to perform this operation on all single pre-defined category nodes. The mapping between control levels and categories can be obtained by using the get-state method.

url-filter/vsys/profiles/profile/category/pre-defined/action

Action of a pre-defined category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/profiles/profile/category/pre-defined/action/all-category

All actions of a predefined category. Three options are available: allow, alert, and block.

NOTE:

The northbound mechanism of this node is faulty. You are advised to perform this operation on all single pre-defined sub-category nodes.

url-filter/vsys/profiles/profile/category/pre-defined/action/category

Category of a pre-defined category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/profiles/profile/category/pre-defined/action/category/name

Name of a pre-defined category. The id of a pre-defined category ranges from 1 to 100 and the id of a pre-defined sub-category ranges from 101 to 60,000.

NOTE:

The northbound mechanism of this node is faulty. You are advised to perform this operation on all single pre-defined sub-category nodes. The mapping between pre-defined categories and pre-defined sub-categories can be obtained by using the get-state method.

url-filter/vsys/profiles/profile/category/pre-defined/action/category/action

Category action of a specified pre-defined category. Three options are available: allow, alert, and block.

url-filter/vsys/category

Category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/category/user-defined

User-defined category of a URL category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/category/user-define/category

Single category of a user-defined URL category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/category/user-define/category/name

Name of a user-defined category. The length is 1 to 32 characters. If the name contains spaces, it must be enclosed with double quotation marks (""), for example, "user for test".

url-filter/vsys/category/user-define/category/description

Description of a user-defined category. The value contains a maximum of 128 characters.

url-filter/vsys/category/user-define/category/match-rule

Indicates that the operation request object is the current matching rule. It contains only subnodes and has no data significance.

url-filter/vsys/category/user-define/category/match-rule/match-scope

See: url-filter/vsys/profiles/profile/whitelist/match-rule/match-scope.

url-filter/vsys/category/user-define/category/match-rule/match-type

See: url-filter/vsys/profiles/profile/whitelist/match-rule/match-type.

url-filter/vsys/category/user-define/category/match-rule/value

See: url-filter/vsys/profiles/profile/whitelist/match-rule/value.

url-filter/vsys/category/pre-defined

Pre-defined category of a URL category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/category/pre-defined/subcategory

Category of a pre-defined URL category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter/vsys/category/pre-defined/subcategory/name

Name of a pre-defined sub-category. The id of a pre-defined category ranges from 1 to 100 and the id of a pre-defined sub-category ranges from 101 to 60,000.

url-filter/vsys/category/pre-defined/subcategory/match-rule

Indicates that the operation request object is the current matching rule. It contains only subnodes and has no data significance.

url-filter/vsys/category/pre-defined/subcategory/match-rule/match-scope

See: url-filter/vsys/profiles/profile/whitelist/match-rule/match-scope.

url-filter/vsys/category/pre-defined/subcategory/match-rule/match-type

See: url-filter/vsys/profiles/profile/whitelist/match-rule/match-type.

url-filter/vsys/category/pre-defined/subcategory/match-rule/value

See: url-filter/vsys/profiles/profile/whitelist/match-rule/value.

url-filter-state

Indicates that the operation request object is URL filtering profiles. It is only used to contain sub-objects, but does not have any data meaning.

NOTE:

Currently only supports querying all status information, temporarily does not support the query specified status information.

url-filter-state/vsys

Indicates that the operation request object is the system. It is only used to contain sub-objects, but does not have any data meaning.

url-filter-state/vsys/name

Indicates the name of a system, which is in string format.

url-filter-state/vsys/profiles

Indicates that the operation request object is all URL filtering profiles. It is only used to contain sub-objects, but does not have any data meaning.

url-filter-state/vsys/profiles/profile

Indicates that the operation request object is the current URL filtering profile. It is only used to contain sub-objects, but does not have any data meaning.

url-filter-state/vsys/profiles/profile/name

Indicates the name of a URL filtering profile. The value is case-sensitive characters.

  • If the name does not contain spaces, the value is a string of 1 to 32 characters.
  • If the name contains spaces, the value is a string of 3 to 34 characters, and the name must be enclosed with double quotation marks (""), for example, "user for test". The name cannot contain question marks (?), commas (,), and hyphens (-).

url-filter-state/vsys/profiles/profile/reference-count

Number of times a profile is referenced.

url-filter-state/pre-defined-category

Pre-defined category of a URL category.

url-filter-state/pre-defined-category/category

Category of a pre-defined category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter-state/pre-defined-category/category/name

Name of a pre-defined category.

The id of a pre-defined category ranges from 1 to 100 and the id of a pre-defined sub-category ranges from 101 to 60,000.

url-filter-state/pre-defined-category/category/description

Description of a pre-defined category. The value is a string of case sensitive characters including spaces. The value ranges from 1 to 128 characters.

url-filter-state/pre-defined-category/category/subcategory

Category of a pre-defined URL category. It is only used to contain sub-objects, but does not have any data meaning.

url-filter-state/pre-defined-category/category/subcategory/name

Name of a pre-defined sub-category.

The id of a pre-defined category ranges from 1 to 100 and the id of a pre-defined sub-category ranges from 101 to 60,000.

url-filter-state/pre-defined-category/category/subcategory/description

Description of the pre-defined sub-category. The value is a string of case sensitive characters including spaces. The value ranges from 1 to 128 characters.

url-filter-state/default-profile

Indicates that the operation request object is the default profile of the URL. It contains only subnodes and has no data significance.

url-filter-state/default-profile/profile

Indicates that the operation request object is the current URL filtering profile. It contains only subnodes and has no data significance.

url-filter-state/default-profile/profile/name

Name of the URL filtering default configuration profile. The value is a string. The default profile name is default.

url-filter-state/default-profile/profile/description

Description of the URL filtering profile. The value is a string of case sensitive characters including spaces. The value ranges from 1 to 128 characters.

url-filter-state/default-profile/profile/default-action

Default action in the URL filtering profile. Three options are available: allow, alert, and block.

Creating a User-Defined URL Filtering Profile

This section provides a sample of creating a user-defined URL filtering profile using the create method.

NOTE:

After creating a user-defined URL filtering profile, the configuration does not take effect immediately. You need to execute configuration compilation to activate the configuration. Because the activation operation is for all security features, it usually takes a long time, and it is recommended that you complete all security feature configuration before submitting the configuration.

Table 3-1320 Creating a User-Defined URL Filtering Profile

Operation

XPATH

edit-config:create

url-filter/vsys/profiles/profile

Data Requirements
Table 3-1321 Creating a User-Defined URL Filtering Profile

Item

Data

Description

Name (name)

url_profile

Create a user-defined URL filtering profile and set parameters such as default actions, whitelist rules, and blacklist rules.

Description (description)

The description of the URL filter profile

Default action (default-action)

alert

Whitelist rule scope (scope)

host

Whitelist match type (type)

exact

Whitelist rule content (value)

test.com

Blacklist rule scope (scope)

url

Blacklist match type (type)

suffix

Blacklist rule content (value)

*123.com

Filtering action mode

loose

User-defined category name (name)

category_a

User-defined category action (action)

alert

Predefined category control level (control-level)

high

Predefined category name (name)

101

Predefined category action (action)

alert

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <edit-config>
    <target>
      <running/>
    </target>
  <error-option>rollback-on-error</error-option>
    <config>
      <url-filter xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
        <vsys>
          <name>public</name>
            <profiles>
              <profile nc:operation="create">
                <name>url_profile</name>
                <description nc:operation="create">The description of the URL filter profile</description>
                <default-action nc:operation="create">alert</default-action>
                  <whitelist>
                    <match-rule nc:operation="create">
                      <scope>host</scope>
                      <type>exact</type>
                      <value>test.com</value>
                    </match-rule>
                  </whitelist>
                  <blacklist>
                    <match-rule nc:operation="create">
                      <scope>url</scope>
                      <type>suffix</type>
                      <value>*123.com</value>
                    </match-rule>
                  </blacklist>
                  <category>
                    <action-mode nc:operation="create">loose</action-mode>
                      <user-defined>
                        <category>
                          <name>category_a</name>
                          <action nc:operation="create">alert</action>
                        </category>
                      </user-defined>
                      <pre-defined>
                        <level nc:operation="create">high</level>
                          <action>
                            <category>
                              <name>101</name>
                              <action nc:operation="create">alert</action>
                            </category>
                          </action>
                        </pre-defined>
                      </category>
                    </profile>
                  </profiles>
                </vsys>
              </url-filter>
            </config>
          </edit-config>
        </rpc>

Response Example
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <ok/>
</rpc-reply>

Modifying a User-Defined URL Filtering Profile

This section provides a sample of modifying a user-defined URL filtering profile using the replace method.

Table 3-1322 Modifying a user-defined URL filtering profile

Operation

XPATH

edit-config:replace

url-filter/vsys/profiles/profile

Data Requirements
Table 3-1323 Modifying a user-defined URL filtering profile

Item

Data

Description

Name (name)

url_profile

Set the default action and the malicious URL switch for the user-defined configuration file url_profile.

Default action (default-action)

block

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <edit-config>
    <target>
      <running/>
    </target>
  <error-option>rollback-on-error</error-option>
    <config>
      <url-filter xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
        <vsys>
          <name>public</name>
            <profiles>
              <profile>
                <name>url_profile</name>
                <default-action  nc:operation="replace">block</default-action>
              </profile>
            </profiles>
          </vsys>
        </url-filter>
      </config>
    </edit-config>
  </rpc>

Response Example
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <ok/>
</rpc-reply>

Deleting a User-Defined URL Filtering Profile

This section provides a sample of deleting a user-defined URL filtering profile using the delete method.

Table 3-1324 Deleting a user-defined URL filtering profile

Operation

XPATH

edit-config:delete

url-filter/vsys/profiles/profile

Data Requirements
Table 3-1325 Deleting a user-defined URL filtering profile

Item

Data

Description

Name (name)

url_profile

Delete the URL filtering profile url_profile from the public system.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <edit-config>
    <target>
      <running/>
    </target>
  <error-option>rollback-on-error</error-option>
    <config>
      <url-filter xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
        <vsys>
          <name>public</name>
            <profiles>
              <profile nc:operation="delete">
                <name>url_profile</name>
              </profile>
            </profiles>
          </vsys>
        </url-filter>
      </config>
    </edit-config>
  </rpc>
Response Example
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <ok/>
</rpc-reply>

Querying a User-Defined URL Filtering Profile

This section provides a sample of querying a user-defined URL filtering profile using the get-config method.

Table 3-1326 Checking a user-defined URL filtering profile

Operation

XPATH

get-config

url-fiter/vsys/profiles/profile

Data Requirements

None

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <url-filter xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
        <vsys>
          <name>public</name>
            <profiles>
              <profile>
                <name>url_profile</name>
              </profile>
            </profiles>
          </vsys>
        </url-filter>
      </filter>
    </get-config>
  </rpc>
Response Example
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1002">
  <data>
    <url-filter xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter">
      <vsys>
        <name>public</name>
        <profiles>
          <profile>
            <name>url_profile</name>
            <description>The description of the URL filter profile</description>
            <default-action>alert</default-action>
            <blacklist>
              <match-rule>
                <scope>url</scope>
                <type>suffix</type>
                <value>*123.com</value>
              </match-rule>
            </blacklist>
            <whitelist>
              <match-rule>
                <scope>host</scope>
                <type>exact</type>
                <value>test.com</value>
              </match-rule>
            </whitelist>
            <category>
              <action-mode>loose</action-mode>
              <user-defined>
                <all-category>alert</all-category>
              </user-defined>
              <pre-defined>
                <action>
                  <category>
                    <name>101</name>
                    <action>alert</action>
                  </category>
                  <category>
                    <name>108</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>251</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>177</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>109</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>115</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>180</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>181</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>122</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>182</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>183</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>184</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>126</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>190</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>135</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>143</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>240</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>146</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>147</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>149</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>152</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>238</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>155</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>224</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>225</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>156</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>157</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>158</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>231</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>232</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>159</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>254</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>160</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>176</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>226</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>234</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>235</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>237</name>
                    <action>block</action>
                  </category>
                  <category>
                    <name>239</name>
                    <action>block</action>
                  </category>
                </action>
              </pre-defined>
            </category>
          </profile>
        </profiles>
      </vsys>
    </url-filter>
  </data>
</rpc-reply>

Querying the URL Filtering Status

You can view all status information using the get method.

Table 3-1327 Viewing all configured status information

Operation

XPATH

get

url-filter-state

Data Requirements

None

Request Example
<rpc message-id="1013" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <get>
    <filter>
      <url-filter-state xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"></url-filter-state>
    </filter>
  </get>
</rpc>
Response Example
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1013">
  <data>
    <url-filter-state xmlns="urn:huawei:params:xml:ns:yang:huawei-url-filter">
      <vsys>
        <name>public</name>
        <profiles>
          <profile>
            <name>urkk_profile</name>
            <reference-count>0</reference-count>
          </profile>
          <profile>
            <name>url_profile</name>
            <reference-count>0</reference-count>
          </profile>
          <profile>
            <name>default</name>
            <reference-count>0</reference-count>
          </profile>
        </profiles>
      </vsys>
      <vsys>
        <name>vsys1</name>
        <profiles>
          <profile>
            <name>default</name>
            <reference-count>0</reference-count>
          </profile>
        </profiles>
      </vsys>
      <vsys>
        <name>vsys2</name>
        <profiles>
          <profile>
            <name>default</name>
            <reference-count>0</reference-count>
          </profile>
        </profiles>
      </vsys>
      <profile>
        <name>default</name>
        <default-action>allow</default-action>
        <category>
          <action-mode>strict</action-mode>
        </category>
      </profile>
    </url-filter-state>
  </data>
</rpc-reply>
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100022096

Views: 8287

Downloads: 69

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next