Appendix A - Uniform Resource Identifier : Non-routable Addresses
 
Share this page                  
Non-routable Addresses
Some URI groups are reserved for specific purposes such as private networks where it is not required to expose an individual computer or group of computers directly to the web. The following three groups of addresses are reserved for this:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
The non-routable IP addresses are used, network routers within the organization route the traffic with Native Address Translation (NAT) using Dynamic Host Control Protocol (DHCP). Because the non-routable IP groups are not registered in the Internet router and domain name server tables, the local router assigns identifying code to the packet headers it receives from local machines. The local router uses these identifiers to direct traffic from and to local computers. Non-routable addresses provide an additional layer of security.
Example
A valid internet URL is structured as follows:
scheme://[username:password@]domainname:portnumber/path
where:
scheme - The access protocol (service) such as HTTP, or FTP.
:(colon) - Informs the scheme that everything which follows the colon is the host name in RFC1037 format until the third slash (/)
username:password@ - User name and password are optional.
:portnumber - If port is not specified, then scheme uses the default port and the second colon is not used.
/ - The third slash informs the scheme that everything which follows the slash is the hierarchical path to the resource, including file name
Note:  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.
Example
The URL http://www.domainname.com/file.htm may not locate http://www.domainname.com/File.html and returns "Error 404-Resource Not Found" or defaults to the domain error page.
Current URI support using Map Designer:
http://[address]
https://[address]
file:///[path to file]
ftp://[server]/[path to file]
djmessage:///[name of message object]
gzip:///[path to gzip file]
 
 
 
The following is also supported:
djstream:///[path to dll]
stdin:///
stdout:///
stderr:///
anythingelse:///