No, no, no, no, no. A
web server is
not a
file server!
What you've actually done is tell Tomcat that your entire
webapp is located in the C:\files directory. That is, your exploded WAR is C:\files and the context that you deployed to Tomcat under was "/files".
Because the default action for ".jpg" resources in Tomcat is to retrieve them, the URL
http://localhost:8085/files/test.jpg should, in fact display the contents of C:\files\test.jpg in your browser window.
Subject to the following limitations:
1. You have configures Tomcat to respond to http requests on port 8085. The default http port is 8080.
2. The Tomcat server process has read-access rights to file C:\files\test.jpg.
Getting a "404" error generally indicates that you've made condition #1 happy, so I'd check the users and groups settings on the test.jpg file and on the C:\files directory against the user/group configuration that Tomcat's running under.