Sorry if I was vague.
The server returns a 404 error when a jsp file is hit that is below a directory which is a symbolic link. For instance /filesystem/webs/approot/shared is a symlink to /filesystem/webs/shared and foo.jsp exists in shared. When "http://server/shared/foo.jsp" is hit the server returns a 404. The server does however return a succesful directory listing of "http://server/shared/".
Thanks,
Jess
hi
using the WS7 Technology Preview 3 build, this works fine for me. for e,g. i have a web app in my home directory and created a symbolic link to /tmp/foo. now, if I mention
<path>/tmp/foo</path> in the server instance's server.xml , the index.jsp gets loaded successfully .
you might want to check out whether the symolic link is indeed accessible in your case.
for eg
ls -la original file symbolic link_file
cat orgiinal file
cat symbolic link_file
last but not least, you can consider using WS7's latest TP3 (technology preview 3), if u r not using it already.
pl. note that WS7 TP3 is not upgradable from WS7 TP2 but supports upgrading from 6.1
i thought i already repled to this.
hey, i am not able to reproduce this bits. I consruct a web app in my home directory and then place a symlink to /tmp . now, if I use /tmp/foo as the <path> in my server.xml, the index.jsp loads fine.
in your case, check out the following
- try using the latest web server 7 TP3 release. pl. note that this release does not support upgrading from TP2 but does support upgrading from 6.1
- ensure that the symbolic link is indeed pointing to the right files and is indeed accessible.
Okay, I upgraded to TP3 and still the same issue. It sounds to me that in your test you are symlinking your approot, this works fine for me. The problem arises when the symlink occurs below the docroot.
/filesystem/webs/approot/shared --> /filesystem/webs/shared
(so the link is to a directory on the same level as the approot, and is not in the approot)
and the jsp exists in /filesystem/webs/shared so the URI would be:
/shared/foo.jsp
We are trying to do this so we can share jsps (and other such files) between multiple web applications. So, approot, approot2, approot3 and approot4 would all have access to this subset of jsps that are in the shared directory.
thanks,
jess