>> Here is the website in question: >> http://www.okcca.net/online/
>You can't tell where things are by looking from the outside; the URLs used to access the web site can be easily mapped to >various locations in the file system by servlet-mappings, appBase and docBase attributes, filters, symbolic links, etc. A >well-designed and well-managed web site will have such things documented, but unfortunately many just seem to evolve. Ok, I understand what you are saying about not seeing the location from the outside. However, am I wrong in thinking that I can track down the location if I know where everything is residing? For example, if I click on the "judges for retention" link on the left side of the main webpage the browser is directed to an address of: http://www.okcca.net/online/JudgeVote.2006.jsp I know that the "online" directory resides in the /usr/local/src/jakarta-tomcat-5.5.9/webapps/ directory and therefore the "JudgeVote.2006.jsp" file should be in that online directory. When I navigate to that directory on the server I can see that file. Therefore, I have been looking at each page/link in this manner. I look at the address location in the web browser and then navigating to the appropriate directory in the /usr/local/src/. . . directory I believe it is on the server to verify that the file in question is there. So far this has worked in showing me the exact directory location for each page/link I have looked at. Is this a legitimate way to go about this or am I going to overlook something in using this method? As far as your comment about documentation, I am afraid I have not come across any documentation detailing any of the website design. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
