• SonicOS 7
• Zones
  • How Zones Work
  • Predefined Zones
  • Security Types
  • Allow Interface Trust
  • Enabling SonicWall Security Services on Zones
  • Effect of Wireless and Non-Wireless Controller Modes
    • Effects of Enabling Non-Wireless Controller Mode
    • Effects of Enabling Wireless Controller Mode
  • Match Objects > Zones
    • The Zone Settings Table
    • Adding a New Zone
    • Configuring a Zone for Guest Access
    • Configuring a Zone for Open Authentication and Social Login
    • Configuring a Zone for Captive Portal Authentication with RADIUS
    • Configuring a Zone for Customized Policy Message
    • Configuring a Zone for Customized Login Page
    • Configuring the WLAN Zone
    • Configuring the RADIUS Server
    • Configuring DPI-SSL Granular Control per Zone
    • Enabling Automatic Redirection to the User-Policy Page
    • Deleting a Zone
• Addresses
  • Types of Address Objects
  • About Address Groups
  • About UUIDs for Address Objects and Groups
  • Addresses Page
    • Common Features
      • Common Functions
      • Common Column Headings
    • Sorting the Entries
  • Default Address Objects and Groups
  • Default Pref64 Address Object
  • Default Rogue Address Groups
  • Adding an Address Object
  • Editing Address Objects
  • Deleting Custom Address Objects
  • Purging MAC or FQDN Address Objects
  • Creating Address Groups
  • Editing Address Groups
  • Deleting Address Groups
  • Working with Dynamic Address Objects
    • Key Features of Dynamic Address Objects
    • Enforcing the Use of Sanctioned Servers on the Network
    • Using MAC and FQDN Dynamic Address Objects
      • Blocking All Protocol Access to a Domain using FQDN DAOs
      • Using an Internal DNS Server for FQDN-based Access Rules
      • Controlling a Dynamic Host’s Network Access by MAC Address
      • Bandwidth Managing Access to an Entire Domain
• Services
  • About Default Service Objects and Groups
  • Predefined IP Protocols for Custom Service Objects
  • Adding Service Objects using Predefined Protocols
  • Adding Custom IP Type Services
    • Configuration Example
  • Editing Custom Service Objects
  • Deleting Custom Service Objects
  • Adding Custom Service Groups
  • Editing Custom Service Groups
  • Deleting Custom Service Groups
• URI Lists
  • About URIs and the URI List
  • About URI List Groups
  • About Keywords and the Keyword List
  • Matching URI List Objects
  • Using URI List Objects
  • Managing URI List Objects
    • About the URI List Objects Table
    • Configuring URI List Objects
    • Exporting a URI List Object
    • Editing a URI List Object
    • Deleting URI List Objects
  • Managing URI List Groups
    • About the URI List Groups Table
    • Adding URI List Groups
    • Editing a URI List Group
    • Deleting URI List Groups
• Match Objects
  • About Match Objects
    • About Regular Expressions
      • Regular Expression Syntax
    • About Negative Matching
  • About Application List Objects
    • About Application Filters
    • About Category Filters
  • Configuring a Match Object
  • Configuring Application List Objects
• Schedules
  • Adding a Custom Schedule
  • Modifying Schedules
  • Deleting Custom Schedules
• Dynamic Group
  • About the Dynamic External Address Group File
  • DEAG and DEAO Maximums
  • High Availability Requirements
  • Adding a Dynamic External Object
  • Editing Dynamic External Objects
  • Deleting Dynamic External Objects
• Email Addresses
  • Configuring Email Address Objects
• SonicWall Support
  • About This Document

About URIs and the URI List

Each URI List Object must have at least one URI in its URI List. You can manually add entries to the URI List by typing or pasting them in, or you can import a list of URIs from a text (.txt) file. The file can be created manually, or can be a file that was previously exported from the appliance. Each URI in the file is on its own line.

You can export the URI List contents into a text file that you can import later.

The URIs and URI List have the following requirements:

• Each URI can be up to 255 characters.
• The maximum combined length of all URIs in one URI List is 131,072 (1024*128) characters, including one character for each new line (carriage return) between the URIs.
• By definition, a URI is a string containing host and path. Port and other content are currently not supported, but you can use Keywords to match these.
• The host portion of a URI can be an IPv4 or IPv6 address string.

• Each URI can contain up to 16 tokens. A token in a URI is a string composed of the characters:

  • 0 through 9
  • a through z
  • A through Z
  • $ - _ + ! ' ( ) , .
  • Each token can be up to 64 characters, including one character for each separator (. or /) surrounding the token.
  • An asterisk (*) can be used as a wildcard representing a sequence of one or more valid tokens, not one or more characters.

  Examples of valid URIs	Examples of invalid URIs
  news.example.com news.example.com/path news.example.com/path/abc.txt news.*.com/*.txt 10.10.10.10 10.10.10.10/path [2001:2002::2003]/path [2001:2002::2003:*:2004]/path/*.txt	Using the wildcard character (*) incorrectly can result in invalid URIs such as: example*.com exa*ple.com example.*.*.com The wildcard character represents a sequence of one or more tokens, not one or more characters.