Ok after some mucking about, redeploying and whatnot, here's where I'm at; If I use the IP/folder/subfolder it now works as it's supposed to. Folder is the deployed apps base folder, subfolder is the broken folder.
So, bypassing apache2/jkmod now seems to fix the issue, but not when using the url (thus with apache2 and jkmod) as tomcat then throws the 404. Why it's *tomcat* that throws the error is beyond me, I though all that happened was that it transfers the traffic from apache to tomcat, I don't understand how it can work with the direct IP/folder but not with URL. However, it does help narrow down the problem. I'm still at a loss but slowly gaining some info. On Apr 14, 4:08 pm, Trenatos <[email protected]> wrote: > I just created a brand new project, made a few files and a subfolder, > exported to WAR and deployed, and the subfolder works for it. > > Bypassing apache/jk doesn't fix it, the 404 is definitely purely > tomcat. > I checked the welcome/index and it seems fine. > > I guess the problem is that it doesn't know what/when to let the > servlet do the processing. > > Logs doesn't seem to show any issues. > > On Apr 14, 3:27 pm, Matthew Woodward <[email protected]> wrote: > > > > > > > > > On Sat, Apr 14, 2012 at 1:14 PM, Trenatos <[email protected]> wrote: > > > Anyway, last night I went and updated a file in a subfolder of a live > > > site, when I went to use it, I got a 404 on the folder it's in. > > > What do the logs say? Sometimes when you see a 404 it actually means a file > > permission issue. Or if it's index.cfm specifically but shows up when you > > type it in manually then that's just an issue with that not being in the > > welcome/index file list (though sounds like you have other issues going on > > as well). > > > > So if I manually type in the url, add the subfolder, and a filename > > > (.cfm) it gives me the file as if it was a textfile. > > > That sounds like a servlet mapping or a proxying issue. How you got there I > > can't say but since you see the file spit out as plain text that typically > > means Tomcat doesn't know it's supposed to hand off cfm processing to the > > cfm servlet. > > > Since you're proxying are there any Apache or proxy settings that would > > cause any issues? Without knowing a lot more about specifically what you > > did to get in this situation as well as all your settings there's a ton of > > possibilities. > > > Can you hit the file directly on the Tomcat port (i.e. bypass Apache and > > any proxying you're doing entirely), and if so does that work? If it does, > > then it's a proxying issue. If you still see plain text it's a servlet > > mapping issue. > > > -- > > Matthew Woodward > > [email protected]http://blog.mattwoodward.com > > identi.ca / Twitter: @mpwoodward > > > Please do not send me proprietary file formats such as Word, PowerPoint, > > etc. as attachments.http://www.gnu.org/philosophy/no-word-attachments.html -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en
