A Uri Is similar to a URL string. URI is known as a Uniform Resource Identifier, and is used to identify assets and their locations rather than a webpage or site. Since website images are assets in Resonite, URLs are commonly misconceived as being URIs.
For how URI's pointing to Assets are gathered and marked as "Don't clean this data up" by the cloud, see Asset Saving.
URI Fields with a URI in them for an asset will not download or try to load the asset data unless that URI field is part of an IAsset type component. Asset Saving mentions the data will never be lost, but the user just wont download the data until it is part of an Asset component. But when the item is uploaded and the data isnt on the cloud for an asset; if the user already has a local copy then a transfer of the asset data will start.
Technical
Input And Fields
When typing into any field of this type, make sure that it is formatted correctly or it will fail, examples include:
http://www.google.com/
http://127.0.0.1/
Inputs that will fail if entered like this (or revert back to the last known valid input, including null):
www.google.com
127.0.0.1
localhost
Port Numbers
When entered correctly, port numbers can be added to the URI string like this: http://127.0.0.1:5000/
- (TODO: Why is
http://127.0.0.1:80/
not valid? Might need "https")
HTTP/HTTPS
Both http
and https
while part of the URI string is valid.
IPv6
For imputing an IPv6 in a URI field, here is what it should look like:
http://[2606:2800:21f:cb07:6820:80da:af6b:8b2c]/
(Leads to example.com)http://[0000:0000:0000:0000:0000:0000:0000:0001]
,http://[0:0:0:0:0:0:0:1]
, orhttp://[::1]
(loopback address)
See Also
- Wikipedia's definition on Uniform Resource Identifier (URI)
- Wikipedia's definition on Uniform Resource Locator (URL)
- Wikipedia's definition on IPv4
- Wikipedia's definition on IPv6