RE: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Try to point your documentroot to point somewhere else and try ... -Original Message- From: Stanislav Bauer [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 08:46 To: Tomcat Users List Subject: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 Hi, I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Thanx - 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]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
No its no a problem of finding the right file. It shows the right one, i.e. index.jsp but it shows the source and does not execute it. It seems to be for dynamic pages. For instance I have a response.Redirect() in index.jsp. SB Raghupathy,Gurumoorthy wrote: Try to point your documentroot to point somewhere else and try ... -Original Message- From: Stanislav Bauer [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 08:46 To: Tomcat Users List Subject: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 Hi, I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Thanx - 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]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi Stanislav, Stanislav Bauer schrieb: I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Sounds like the pages, where the source code is displayed instead of the result of the processed jsp file, are served by the Apache server itself and not by Tomcat as intended. This is possible because the DocumentRoot of your Apache seems to point directly to your Tomcat web application's directory. It is difficult to tell you more as you don't give a lot of information. Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Can you tell me the listing of the /.../webapps/domain directory ? Regards Guru -Original Message- From: Stanislav Bauer [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 09:08 To: Tomcat Users List Subject: Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 No its no a problem of finding the right file. It shows the right one, i.e. index.jsp but it shows the source and does not execute it. It seems to be for dynamic pages. For instance I have a response.Redirect() in index.jsp. SB Raghupathy,Gurumoorthy wrote: Try to point your documentroot to point somewhere else and try ... -Original Message- From: Stanislav Bauer [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 08:46 To: Tomcat Users List Subject: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 Hi, I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Thanx - 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]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
OK, which information would help you. Is it necessary to point the DocumentRoot somwhere else? I thought it doesnt matter where the sources lie. Btw you are right, I point DocumentRoot directly to webapps under TC, so I dont have to have it twice. Thanx SB Lutz Zetzsche wrote: Hi Stanislav, Stanislav Bauer schrieb: I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Sounds like the pages, where the source code is displayed instead of the result of the processed jsp file, are served by the Apache server itself and not by Tomcat as intended. This is possible because the DocumentRoot of your Apache seems to point directly to your Tomcat web application's directory. It is difficult to tell you more as you don't give a lot of information. Best wishes Lutz - 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]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
/META-INF /WEB-INF various subfolders in the root, ie /domain I have index.jsp (also /domain/index.jsp) which should redirect to a subfolder. /.../webapps/domain is a standard structure of a TC WebApp. Its a small app with majorly static *.jsp pages which are displayed fine. Just two, where it seems to be some jsp-action are displayed as source. In apaches httpd.conf I also added index.jsp to the DirectoryIndex. SB Raghupathy,Gurumoorthy wrote: Can you tell me the listing of the /.../webapps/domain directory ? Regards Guru -Original Message- From: Stanislav Bauer [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 09:08 To: Tomcat Users List Subject: Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 No its no a problem of finding the right file. It shows the right one, i.e. index.jsp but it shows the source and does not execute it. It seems to be for dynamic pages. For instance I have a response.Redirect() in index.jsp. SB Raghupathy,Gurumoorthy wrote: Try to point your documentroot to point somewhere else and try ... -Original Message- From: Stanislav Bauer [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 08:46 To: Tomcat Users List Subject: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 Hi, I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Thanx - 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]
RE: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi there, I also find a similar problem with my set up here (although it's more consistant and I can make it do it, but don't know how to fix it really! I run apache 1.3.33 / mod_ssl 2.8.22 and Tomcat 3.3.2 with mod_jk 1.2.10, mod_security is also compiled in but disabled as a module. If I go to www.domain.com/context/index.jsp I get a page as expected If I go to www.domain.com//context/index.jsp I get the source code, also this isn't just on one context or the index.jsp file, we run quite a few contexts and it consistently displays source code if you put double (or more) slashes in the URL before the context. Alias /context/ /www/content/www.domain.com/webapps/context/ JkMount /context/*.jsp lb-332 JkMount /context/servlet/* lb-332 Where lb-332 is the connector defined in workers.properties This only happens though for any context which is 'split' between Apache and Tomcat, if for instance I send everything to tomcat by using Any suggestions? Regards John Boocock -Original Message- From: Lutz Zetzsche [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 09:13 To: Tomcat Users List Subject: Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 Hi Stanislav, Stanislav Bauer schrieb: I'm trying to connect Apache with TC to serve www.domain.com for instance. I have a VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost But for certain pages I get the source code instead of the TC result. Wat directive I a have to use? Directly with :8080 the pages are fine. Sounds like the pages, where the source code is displayed instead of the result of the processed jsp file, are served by the Apache server itself and not by Tomcat as intended. This is possible because the DocumentRoot of your Apache seems to point directly to your Tomcat web application's directory. It is difficult to tell you more as you don't give a lot of information. Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This email has been scanned for all viruses by the MessageLabs SkyScan service. ** This email and any files transmitted with it are confidential, and may be subject to legal privilege, and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error or think you may have done so, you may not peruse, use, disseminate, distribute or copy this message. Please notify the sender immediately and delete the original e-mail from your system. Computer viruses can be transmitted by e-mail. Recipients should check this e-mail for the presence of viruses. The Capita Group and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi Stanislav, Stanislav Bauer schrieb: In apaches httpd.conf I also added index.jsp to the DirectoryIndex. oh, bad idea! As Apache shouldn't serve jsp pages itself, you shouldn't instruct Apache to look for an index.jsp in case of a request like http://www.domain.com/dir/. Remove index.jsp from the DirectoryIndex, reload Apache and have a look if your problem is solved then. However, you should re-think your server configuration completely. I don't think that it is a good idea to mix Apache and Tomcat too much. There are several security implications. I.e. mis-configurations will allow the servers to access each other's sensitive configuration files. Tomcat may be able to read Apache's htaccess files, Apache may be able to read Tomcat's web.xml etc. I don't know why you have pointed Apache's DocumentRoot to your Tomcat web application directory but if this is not necessary, you shouldn't do it. Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hmm, when I remove index.jsp then I get just a directory listing. Concerning the mining, how should the structure be then? Where should DocumentRoot normaly point to? I thought it works that way: 1) Take the pages from DocumentRoot 2) If it is *.jsp pass it to TC and TC will execute them 3) Otherwise Apache sends them directly But it seams that Apache sends all directly, and if I dont have the DirectoryIndex with index.jsp it starts with a listing. Thanks SB Lutz Zetzsche wrote: Hi Stanislav, Stanislav Bauer schrieb: In apaches httpd.conf I also added index.jsp to the DirectoryIndex. oh, bad idea! As Apache shouldn't serve jsp pages itself, you shouldn't instruct Apache to look for an index.jsp in case of a request like http://www.domain.com/dir/. Remove index.jsp from the DirectoryIndex, reload Apache and have a look if your problem is solved then. However, you should re-think your server configuration completely. I don't think that it is a good idea to mix Apache and Tomcat too much. There are several security implications. I.e. mis-configurations will allow the servers to access each other's sensitive configuration files. Tomcat may be able to read Apache's htaccess files, Apache may be able to read Tomcat's web.xml etc. I don't know why you have pointed Apache's DocumentRoot to your Tomcat web application directory but if this is not necessary, you shouldn't do it. Best wishes Lutz - 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]
RE: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi John, Boocock, John (CSS) schrieb: If I go to www.domain.com/context/index.jsp I get a page as expected If I go to www.domain.com//context/index.jsp I get the source code, also this isn't just on one context or the index.jsp file, we run quite a few contexts and it consistently displays source code if you put double (or more) slashes in the URL before the context. Alias /context/ /www/content/www.domain.com/webapps/context/ JkMount /context/*.jsp lb-332 JkMount /context/servlet/* lb-332 1. The above Alias in the Apache conf points to the Tomcat webapps directory. That means, Apache can access the files of the tomcat web application. 2. //context/ does not match the above JkMount patterns which start with /context/. That means, Apache does not forward a request like www.domain.com//context/index.jsp to Tomcat. The result from both is that Apache processes requests like www.domain.com//context/index.jsp itself. If it can find and access the requested file, Apache will serve it. Due to the fact, that your Apache has no module installed to process jsp files, it just serves the jsp files plain-text. That's the solution from my point of view. I would recommend not to point to any sub directory of $CATALINA_HOME with a DocumentRoot or Alias in Apache's conf to avoid such security breaches. Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Maybe it would be sufficient to write JkMount differently but I dont know how for matching http://www.domain.com The examples seam to be written just for test scenarios, but not if you arrive to the server with http://www.domain.com Thanks SB Lutz Zetzsche wrote: Hi Stanislav, Stanislav Bauer schrieb: In apaches httpd.conf I also added index.jsp to the DirectoryIndex. oh, bad idea! As Apache shouldn't serve jsp pages itself, you shouldn't instruct Apache to look for an index.jsp in case of a request like http://www.domain.com/dir/. Remove index.jsp from the DirectoryIndex, reload Apache and have a look if your problem is solved then. However, you should re-think your server configuration completely. I don't think that it is a good idea to mix Apache and Tomcat too much. There are several security implications. I.e. mis-configurations will allow the servers to access each other's sensitive configuration files. Tomcat may be able to read Apache's htaccess files, Apache may be able to read Tomcat's web.xml etc. I don't know why you have pointed Apache's DocumentRoot to your Tomcat web application directory but if this is not necessary, you shouldn't do it. Best wishes Lutz - 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]
RE: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi and thanks for the quick response 1. On point one, I appreciate that and it's deliberate to get apache serving the static content without the need to do anything particularly fancy in terms of where files are stored etc. Especially as we run 3.3.2 which isn't exactly blindingly fast for static content! :) 2. I understand that is what's causing the problem, but am unsure really of a way to fix it properly. Any suggestions on better pattern matching for the JkMount as I'm not quite sure on how flexible it is with regex, etc.? I've tried in the past to get around the problem with mod_security but it seems that it can't stop this because apache is normalising the paths so Mod_sec can't do anything about then but then when the request goes to Tomcat it regards, quite rightfully, that the connection doesn't go to through the connector because the pattern doesn't match. Regards John Boocock -Original Message- From: Lutz Zetzsche [mailto:[EMAIL PROTECTED] Sent: 13 May 2005 10:21 To: Tomcat Users List Subject: RE: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12 Hi John, Boocock, John (CSS) schrieb: If I go to www.domain.com/context/index.jsp I get a page as expected If I go to www.domain.com//context/index.jsp I get the source code, also this isn't just on one context or the index.jsp file, we run quite a few contexts and it consistently displays source code if you put double (or more) slashes in the URL before the context. Alias /context/ /www/content/www.domain.com/webapps/context/ JkMount /context/*.jsp lb-332 JkMount /context/servlet/* lb-332 1. The above Alias in the Apache conf points to the Tomcat webapps directory. That means, Apache can access the files of the tomcat web application. 2. //context/ does not match the above JkMount patterns which start with /context/. That means, Apache does not forward a request like www.domain.com//context/index.jsp to Tomcat. The result from both is that Apache processes requests like www.domain.com//context/index.jsp itself. If it can find and access the requested file, Apache will serve it. Due to the fact, that your Apache has no module installed to process jsp files, it just serves the jsp files plain-text. That's the solution from my point of view. I would recommend not to point to any sub directory of $CATALINA_HOME with a DocumentRoot or Alias in Apache's conf to avoid such security breaches. Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This email has been scanned for all viruses by the MessageLabs SkyScan service. ** This email and any files transmitted with it are confidential, and may be subject to legal privilege, and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error or think you may have done so, you may not peruse, use, disseminate, distribute or copy this message. Please notify the sender immediately and delete the original e-mail from your system. Computer viruses can be transmitted by e-mail. Recipients should check this e-mail for the presence of viruses. The Capita Group and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi Stanislav, Stanislav Bauer schrieb: Hmm, when I remove index.jsp then I get just a directory listing. Concerning the mining, how should the structure be then? Where should DocumentRoot normaly point to? I thought it works that way: 1) Take the pages from DocumentRoot 2) If it is *.jsp pass it to TC and TC will execute them 3) Otherwise Apache sends them directly But it seams that Apache sends all directly, and if I dont have the DirectoryIndex with index.jsp it starts with a listing. Ok, the directory listing also tells you which server serves the listing. I assume, it is Apache and not Tomcat, isn't it? Normally, you use Apache to serve PHP pages and Tomcat to server JSP pages. Sometimes you want, that Apache receives the requests for Tomcat and forwards them to Tomcat. Both ways, you have different web applications which you should keep separately as regards the directories. The DocumentRoot of Apache should never point to a subdirectory of $CATALINA_HOME, and the webApp and docBase attributes of Tomcat should never point to Apache directories. In my opinion. It is up to you where to point to with the DocumentRoot. I.e. /var/www/html/ or where you have your PHP web application, if you have one. All pages within Tomcat's webapp directory should be served by Tomcat. Finally, I have had a second look at the lines you have sent: VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost 1. What happens if you remove JkAutoAlias? 2. What happens if you set DocumentRoot to /.../webapps/? (Both just for a moment to see what happens. :-) ) Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
OK, First thanks for the patience. I have now a config that seams to work but: 1) I have a second domain pointing to the same IP, say www.domain2.com 2) I put JkMount /domain/* worker1 into IfModule mod_jk.c, where I have also JkWorkersFile aso 3) Now if I write www.domain2.com/domain I get the right reaction But how to configure that www.domain.com works the same I realy dont know, ie a Virtual Host. I thought it must be something like this, maybe some more directives: VirtualHost ServerName www.domain.com JkMount somthing here, but what? worker1 /VirtualHost SB Lutz Zetzsche wrote: Hi Stanislav, Stanislav Bauer schrieb: Hmm, when I remove index.jsp then I get just a directory listing. Concerning the mining, how should the structure be then? Where should DocumentRoot normaly point to? I thought it works that way: 1) Take the pages from DocumentRoot 2) If it is *.jsp pass it to TC and TC will execute them 3) Otherwise Apache sends them directly But it seams that Apache sends all directly, and if I dont have the DirectoryIndex with index.jsp it starts with a listing. Ok, the directory listing also tells you which server serves the listing. I assume, it is Apache and not Tomcat, isn't it? Normally, you use Apache to serve PHP pages and Tomcat to server JSP pages. Sometimes you want, that Apache receives the requests for Tomcat and forwards them to Tomcat. Both ways, you have different web applications which you should keep separately as regards the directories. The DocumentRoot of Apache should never point to a subdirectory of $CATALINA_HOME, and the webApp and docBase attributes of Tomcat should never point to Apache directories. In my opinion. It is up to you where to point to with the DocumentRoot. I.e. /var/www/html/ or where you have your PHP web application, if you have one. All pages within Tomcat's webapp directory should be served by Tomcat. Finally, I have had a second look at the lines you have sent: VirtualHost ServerName www.domain.com DocumentRoot /.../webapps/domain JkMount /domain worker1 JkMount /domain/* worker1 JkAutoAlias / /VirtualHost 1. What happens if you remove JkAutoAlias? 2. What happens if you set DocumentRoot to /.../webapps/? (Both just for a moment to see what happens. :-) ) Best wishes Lutz - 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]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi Stanislav, Stanislav Bauer schrieb: I have now a config that seams to work but: 1) I have a second domain pointing to the same IP, say www.domain2.com 2) I put JkMount /domain/* worker1 into IfModule mod_jk.c, where I have also JkWorkersFile aso 3) Now if I write www.domain2.com/domain I get the right reaction But how to configure that www.domain.com works the same I realy dont know, ie a Virtual Host. I thought it must be something like this, maybe some more directives: VirtualHost ServerName www.domain.com JkMount somthing here, but what? worker1 /VirtualHost Unfortunately, I don't know enough about your full Apache configuration, but if it works with one domain, it should be no problem to make it work for a second. Do you have a second virtual host for the second domain? If so, why don't you remove the virtual host for the first domain and define the first domain as ServerAlias for the virtual host of the second domain? Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
So I'm working now with just one domain :-), say www.domain.com. But instead to go directly to the jsp-webapp I have to write www.domain.com/contextname/ with virtualhost like this: VirtualHost ServerName www.domain.com JkMount /contextname/* worker1 /VirtualHost Then the JSP-pages work like expected. But how is it possible to go directly to the context, ie with www.domain.com? I thought something like this: VirtualHost ServerName www.domain.com JkMount /* worker1 /VirtualHost but then I end up at the manager. I wonder if it is possible at all? Regards SB Lutz Zetzsche wrote: Hi Stanislav, Stanislav Bauer schrieb: I have now a config that seams to work but: 1) I have a second domain pointing to the same IP, say www.domain2.com 2) I put JkMount /domain/* worker1 into IfModule mod_jk.c, where I have also JkWorkersFile aso 3) Now if I write www.domain2.com/domain I get the right reaction But how to configure that www.domain.com works the same I realy dont know, ie a Virtual Host. I thought it must be something like this, maybe some more directives: VirtualHost ServerName www.domain.com JkMount somthing here, but what? worker1 /VirtualHost Unfortunately, I don't know enough about your full Apache configuration, but if it works with one domain, it should be no problem to make it work for a second. Do you have a second virtual host for the second domain? If so, why don't you remove the virtual host for the first domain and define the first domain as ServerAlias for the virtual host of the second domain? Best wishes Lutz - 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]
Re: mod_jk shows source - Apache 2.0.53 mod_jk 1.2.12
Hi Stanislav, Stanislav Bauer schrieb: So I'm working now with just one domain :-), say www.domain.com. But instead to go directly to the jsp-webapp I have to write www.domain.com/contextname/ with virtualhost like this: VirtualHost ServerName www.domain.com JkMount /contextname/* worker1 /VirtualHost Then the JSP-pages work like expected. But how is it possible to go directly to the context, ie with www.domain.com? I thought something like this: VirtualHost ServerName www.domain.com JkMount /* worker1 /VirtualHost but then I end up at the manager. I wonder if it is possible at all? Does the Manager also appear when you try http://www.domain.com:8080/ ? Best wishes Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
