RE: mod_jk/apache+tomcat/400 bad request
Yup, I should be using a local context -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: 21 February 2008 15:26 To: Tomcat Users List Subject: RE: mod_jk/apache+tomcat/400 bad request > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Subject: RE: mod_jk/apache+tomcat/400 bad request > > You might want to put a element into your > server.xml inside the relevant : Perhaps you haven't been keeping up with the last few years of Tomcat releases. As noted, in bold, in the Tomcat docs: http://tomcat.apache.org/tomcat-6.0-doc/config/context.html "For Tomcat 6, unlike Tomcat 4.x, it is NOT recommended to place elements directly in the server.xml file." That statement has been in there since the 5.0 days. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk/apache+tomcat/400 bad request
Hi, You might want to put a element into your server.xml inside the relevant : -Original Message- From: Tommy Peterson [mailto:[EMAIL PROTECTED] Sent: 20 February 2008 18:48 To: users@tomcat.apache.org Subject: mod_jk/apache+tomcat/400 bad request I just set up Tomcat to talk to Apache for a Java app. I am using virtual hosting with mod_jk. In my Apache config files I have the following: JkMount /thedirectory/*.jsp ajp13 JkMount /*/images/* ajp13 However, I am getting a 400 error. The page is just blank. The directory on Tomcat is mainly the following: /webapps/thedirectory/ /webapps/thedirectory/images/ /webapps/thedirectory/subdirectory/ I need all the files in the /webapps/thedirectory/ to be served by Tomcat. I did have in my Apache configuration: JkMount /thedirectory/*.jsp ajp13 JkMount /*/servlet/* ajp13 I also tried JkMount /thedirectory/*.jsp ajp13 JkMount /thedirectory/images/* ajp13 JkMount /thedirectory/subdirectory/* ajp13 Neither worked. I got the same 400 error in the apache access.log. Incidentally, this came about after I continually got a 404 Access Denied error when trying to access this directory. So I put an index.html file in the /thedirectory/ folder and redirected it to login.jsp, which is the main page for the Java application that Tomcat is suppose to handle. So the index.html page is found and it redirects to the login.jsp. The login.jsp is where the 400 error comes into the scene. Any ideas? Thanks. _ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join This e-mail is confidential and should not be used by anyone who is not the original intended recipient. BioMed Central Limited does not accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of BioMed Central Limited. No contracts may be concluded on behalf of BioMed Central Limited by means of e-mail communication. BioMed Central Limited Registered in England and Wales with registered number 3680030 Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mapping JSP's to outside of the war or expanded folder
We also do this with Velocity (we use Spring MVC rather than JSP) and point our Velocity ResourceLoader to somewhere else on the filesystem (away from any Apache document root so they aren't accessible). This brings benefits of being able to do hot-deploy of content/templates for urgent copy changes, should we need to, ability to work with things like AlFresco, and not having any logic other than minimal presentational logic in the view layer. -Original Message- From: Ralph Goers [mailto:[EMAIL PROTECTED] Sent: 18 February 2008 17:37 To: Tomcat Users List Subject: Re: Mapping JSP's to outside of the war or expanded folder We have a similar need. But doing this with JSPs is very dangerous since they can have java code within them. Instead, using a templating language like Velocity would seem to be a mucn better approach. emerson cargnin wrote: > The policy of our company is to deploy the jsp's separated from the > war file, to allow a finer grained control over deployment. I'm not > very fan of it, but it's something I won't be able to change. So I > need a way to point the following URL's to another place in the file > system. > http://server/[context]/jsp/* > http://server/[context]/css/* > http://server/[context]/html/* > http://server/[context]/images/* > > Thanks > emerson > > On 18/02/2008, David Brown <[EMAIL PROTECTED]> wrote: > >> Once the .war is expanded why would you want to map to JSPs outside of the >> file system package? >> >> emerson cargnin wrote .. >> >>> Hi there >>> >>> We use resin here in my work. Resin allows in its web.xml an element like: >>> >>> >>> /jsp/* >>> c:/resin/resin-2.1.4/apps/ucs/ >>> >>> >>> >>> >>> >>> This can also be used in resin.conf, amking the war more portable. >>> >>> Now we are starting a migration to tomcat. But as far as I know TC >>> doesnt not allow to have the JSP's out side of the war or the expanded >>> war. I did a research a couple of years ago. Did it changed? Is there >>> anyway now of mapping the jsp's of an app to an outside folder? >>> >>> Thanks >>> Emerson Cargnin >>> >>> - >>> To start a new topic, e-mail: users@tomcat.apache.org >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> - >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache2 + Tomcat5 + mod_jk mounting issues
Hi - sorry if this is a repost as I found my email wasn't properly validated, We have a set-up of Apache 2 and Tomcat 5 on our dev server (running Debian). I have a VirtualHost set up that has a JkMount in it that corresponds to a Tomcat webapp (so far so standard), like "JkMount /*webapp* ajpw13" (which is a configured worker). I am also using mod_rewrite; my rewrite.conf contains mappings like "RewriteRule ^/blah/?$ /servlet/blah". These mappings and rewrites work perfectly on my local machine (running XP) and on a colleague's box (running OSX). When we deploy to our Dev server, we find that things almost but don't quite work. We enter a URL, e.g. http://dev.abc.com/blah and, on my machine and my colleague's this gets neatly mapped to the JkMount point. On the Debian box this doesn't happen, and I find myself having to use http://dev.abc.com/servlet/blah to get to the JkMount point. Is there something obvious that I might have done/not done? I've never had this problem before? A suitable Connector is set up in my server.xml too... Thanks, Phil. This email has been scanned by Postini. For more information please visit http://www.postini.com
