Look at this "URI": "\\172.22.1.34\\D:\\File\\test.JPG" —
how it possibly be valid?
You can always read about URL and understand its structure:
http://en.wikipedia.org/wiki/URL[
^].
However, what you have written suggests that you have no idea on how Web works and what HTTP server does, even on the level of the common user, not a software developer.
At such a deep level of confusion, it's hard to explain it… Well, do you think HTTP server shows files? Not exactly, it shows Web pages of different content types, and only some of them are mapped on the file system. Even the files which exist in a file system and are translated by the HTTP server as pages based on one-to-one correspondence do not come at the same names as their name in their native file system. This is a matter of safety: the client cannot get direct access to the file system of the server; the service is abstracted form the file system. The files as URLs are named relative to some Web site's root path, and the root corresponds to the part scheme://domain:port (in terms of the article referenced above, please see). Also, the default index file can be involved.
For example: "http://www.myDomain.com/someFile.html" corresponds to the file "someFile.html" placed in the root directory of the site, and "https://www.myDomain.org:4291/" — to the file like "index.html" or "default.aspx" or something like that (depending on server options) located in (another) site root (probably different from the first example due to different schema and port).
—SA