User Guide > Map Connectors > Types of Connections > URI Connections
Was this helpful?
URI Connections
This section describes how to specify the URI scheme in the Source File/URI field or Target File/URI field of the Map Editor. For more information, see Source File/URI Options and Target File/URI Options.
Uniform Resource Identifier (URI) is an addressing technology from which a Uniform Resource Locator (URL) is created. Types of URIs include URLs that use the http:// and ftp:// protocols.
A complete URI describes the following items, separated by colons (:) and forward slashes (/), and in the order shown:
[protocol]//:[hostname]:[portnumber]/[path]
Note:  The number of forward slashes (/) required for the URI depends on the protocol used. For information, see URI Protocols and Formats.
where:
• [protocol] = The protocol used for accessing the resource (such as HTTP or FTP).
• : (colon) - Informs the scheme that everything after the colon up to the last forward slash (/) is the host name in RFC1037 format.
• [hostname] = The website or computer name and address where the resource resides. For DNS lookup, this value can be a hostname or an IP address.
• [portnumber] = The port number that serves the protocol. If the port number is not specified, the access protocol attempts to connect using the default port for the specified protocol, and the colon (:) is not used. For example, HTTP service uses the default port 80. Therefore, http://hostname:80/filename and http://hostname/filename are valid.
• [path] - The last forward slash (/) informs the scheme that everything after it is the hierarchical path to the resource, including file name.
Note:  [username:password@] can optionally be used for username and password login credentials (if the protocol supports it) as follows: [protocol]:[username:password@][hostname]:[port number][file name]
For more information about URI parameters, see URI Parameters.
URI Protocols and Formats
All file based connectors, scripting functions, and object references are supported.
The following URI formats are supported in the Map Editor. Omit the brackets ([ ]) when specifying the URI scheme in the Source File/URI field or Target File/URI field. For more information, see Source File/URI Options and Target File/URI Options.
The following URI formats are supported in the Map Editor.
• azure:///
• djmessage:///[name of message object]
• djstream:///[path to dll]
• file:///[path to file]
• ftp://[server]/[path to file]
• gcp:///
• googledrive:///
• gzip:///[path to gzip file]
Note:  gzip is a special compressed file format that will be automatically decompressed and the contents used within the map.
• http://[address]
• https://[address]
• s3:///
• stderr:///
• stdin:///
• stdout:///
• anythingelse:///
Additional Notes
• Dynamic content is not supported. You may have to save the web page to disk before parsing it.
• Within the URL, the case and file extension must be correct. If the URL returns "Error 404 Resource Not Found" or another form of this error, verify the case and file extension and retry. For example: The URL http://www.hostname.com/file.htm may not locate http://www.hostname.com/File.html and returns "Error 404-Resource Not Found", or defaults to the domain error page.
URI Parameters
The following table provides the description for the URI parameters.
Parameter
Description
User
User name is optional. Some schemes (for example, FTP) allows to specify user name.
Password
Password is optional. User name is required if password is used. Password follows the user name separated by a colon. The user name and password is followed by a @ sign. For example:
• ftp://@host.com/ - has an empty user name and no password
• ftp://host.com/ - has no user name
• ftp://user:@host.com/ - has a user name called "user" and an empty password.
Within the user name and password field, any ":", "@", or "/" must be escaped.
Host
Fully qualified domain names are a sequence of domain labels, separated by decimals. Each domain label starts and ends with an alphanumerical character and may also contain "-" characters. The last domain label does not start with a digit, though, which syntactically distinguishes all domain names from the IP addresses.
Port
Port number required to establish the connection. The default port number is 80. Most schemes use protocols that have a default port number. To specify a different port, the port number follows hostname and is separated from hostname by a colon (:). For example,
http://somedomain.com:110 means access this host on port 110 instead of the default HTTP port 80.
URL Path
The remaining part consists of data specific to the scheme and is known as the URL path. It provides details of how the specified resource is accessed. The "/" between the host (or port) and the URL path is not part of the URL path. The URL path syntax and how it is interpreted depends on the scheme that is used. For example:
http://somedomain.com/private/myweb/vacation/pix/index.html
In this example, the host server is somedomain.com. The rest of the URI is the URL path.
Escape Characters
Valid URIs require character strings that are consistent with the established standards. Some URIs may contain reserved (non-valid) characters such as a space or a hash. These non-valid characters must be escaped for the URI to be valid.
Whether a character is reserved or not is defined by the URI component it appears in. The syntax for escaping depends on the context. Due to this ambiguous nature, use the reserved or potentially reserved characters with caution, or avoid using them. If you must use them, be aware that the characters that are reserved, the context in which they are reserved, and how to escape the reserved characters.
For example, http://server/directory/file 3 changes to http://server/directory/file%20. The space character is replaced with the percent sign (%) and the ASCII hex value 20.
Note:  The hash ("#", ASCII 23 hex) character is reserved. It is used as a delimiter to separate the URI of an object from a fragment identifier. If the hash character is used as a valid character in a URI, it must be escaped.
For more information, see Uniform Resource Identifiers (URI) at http://www.ietf.org.
Limitations
• Map Designer can connect to sources that can be represented as a file or file stream such as WHOIS and HTTP. It cannot connect to interactive session resources such as TELNET or RLOGIN.
• Sometimes Map Editor times out before connecting due to slow network. To resolve this, add the following line in the [UserInfo] section in the cosmos.ini file:
NetworkTimeout=5
The normal default is 5 seconds. If there are problems connecting, then increase the network timeout value to a number greater than 5.
Last modified date: 09/22/2025