Are there any benefits to doing it that way? I am using tomcat standalone and serving out on prot809, not integrating it in with apache.
c. -----Original Message----- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:47 PM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action Hi, If the DNS is configured for that host, then yeah, you can use it instead of the "localhost". But then you have to change all your <host> to use the same hostname. -Yan -----Original Message----- From: Chris [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:34 PM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action It does. Thanks Yan! What should I specify as my defaultHost in the Engine element? And the name in the Host element? <Engine name="Catalina" defaultHost="localhost" debug="0"> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNameSpaceAware="false"> <Context path="/" docBase="myApp"/> </Host> </Engine> should I make defaultHost and name the actual url of the application? ie www.myApp.com? <Engine name="Catalina" defaultHost="www.myApp.com" debug="0"> <Host name="www.myApp.com" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNameSpaceAware="false"> <Context path="/" docBase="myApp"/> </Host> </Engine> What exactly happens when you do this? Does tomcat look in your hosts file to see where the domain name is mapped? The documentation is a little bit unclear for me. c. -----Original Message----- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:22 PM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action ok, whatever you specify in your path is the context path. if you don't want to have the context been part of your request URL(i.e., www.mycompany.com/action.do instead of www.mycompany.com/myapp/action.do), then you can specify the path="". But if your server is serving more that one webapps, the implication of this is that all other requests that are not assigned to other contexts will be processed using this "default" context. So if you only run one web application, there is nothing to worry about. If you are running multiple web applications, then this is a good place to catch those unassigned requests. Hope this helps:). -Yan -----Original Message----- From: Chris [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 1:03 PM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action Actually Yan, that might be something that I want since I am only serving out one web application and I want it to be mapped to the domain www.myapp.com Is that what specifying <Context path="" docBase="myApp"/> c. -----Original Message----- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 12:51 PM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action I am not sure about <Context path="/" docBase="myApp"/>. I think if you try <Context path="/myApp" docBase="myApp"/>, the container will append a / to the path, i.e., /myApp/***.do. But if you use <Context path="" docBase="myApp"/>, then that's the default webapp path, which is not something you want. But the other thread is a good starting point, take a look at the request header too. -Yan -----Original Message----- From: Chris [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 10:58 AM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action Yan, Thanks for the reply. The context for my application is as follows (well the engine element and onwards): <Engine name="Catalina" defaultHost="localhost" debug="0"> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNameSpaceAware="false"> <Context path="/" docBase="myApp"/> </Host> </Engine> This is not the way it is set up on my windows development box. But everything does work in windows using eclipse and sysdeo tomcat so I don't believe it would have anything to do with my action mappings. I believe it must be a tomcat configuration thing. c. -----Original Message----- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 10:41 AM To: 'Tomcat Users List' Subject: RE: problem with url - extra / appended before action it's hard to say what's causing the problem exactly without knowing your context and your action-mappings. maybe in your action mapping, you have one extra / in front. and tomcat would add that to the requestURL? -Yan -----Original Message----- From: Chris [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 9:56 AM To: [EMAIL PROTECTED] Subject: problem with url - extra / appended before action Hello, I have an application that uses frames. The problem that I am experiencing is that when I go to a page that loads a new frameset all of my links and buttons work correctly - that is they produce the correct url: www.companyname.com/action.do?parameter1=blah . Now when I click one of these links it populates a new page in the frameset, but the links are all messed up. They all include an extra "/" before the action name: www.companyname.com//action.do?parameter=blah <http://www.companyname.com/action.do?parameter=blah> . This extra "/" is also found in the <base href="."/> element for these pages. This problem only occurs when I deploy the application (tomcat standalone no apache involved) onto a linux box. The problem does not occur when I test things on my windows box using eclipse and the tomcat sysdeo plugin. Any idea what is going on here? Thanks, c. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
