> There appears to be confusion about the 'file://' protocol. > > The "file://" protocol is really not a protocol at all, since there > are no client-server communications involved. > This 'false' protocol identifier is simply a 'nice' little feature > that web-browsers implement (URL/URLConnection also > implements this), that provides the means of displaying a > file stored on the client system (or on a drive that is > mounted on the client system). > > The key here is 'client-system'. When you type a "file://" > URL into your browser, your browser goes straight to > your filesystem to get the file. It does not contact a web-server > for this. > > If you want to retrieve a 'file' from a web server, you must > provide a URL that starts with 'http://' (or https://).
That was kind of my point really. The point being this is a browser operation and not a server operation. In other words, the point being communicated to the originator of the question is that this is not a problem with Tomcat, nor something you'd expect Tomcat to take care of, but basically a browser implementation. Protocol can really be used in a broad sense. The "file protocol", if you insist, is a expected behavior pattern among systems. i.e. You _expect_ it to work the same on a SunOS box as on a Linux box or a Windoze box. I don't think there is any confusion just miscommunication in some cases. --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
