URL rewriting solution in FAQ does not do the trick
This is more of an Apache question than a Cocoon question, but hopefully someone will know what I'm doing wrong here. Setup: SPARC Solaris 2.7, Apache 1.3.24 w/mod_webapp (Warp), and Tomcat 4.0.1 Goal: Eliminate cocoon from the URL Constraints: Want all my custom content (XML, stylesheets, etc.) to be removed from the Cocoon tree so I can upgrade Cocoon separately. Must use Apache to receive request. URL mapping has to be done per virtual host. I looked at the FAQ, and followed the instructions. I rebuilt Apache with mod_rewrite enabled, then added the followed code to my httpd.conf: VirtualHostmyhost.mydomain:80 ServerNamemyhost.mydomain DocumentRoot /myhost.mydomain/htmls IfModule mod_rewrite.c RewriteEngine on RewriteLog /var/adm/www/rewrite.log RewriteLogLevel 9 RewriteRule ^/xml /cocoon/xml/ [R] RewriteRule ^/xml(.*) /cocoon/xml$1 [R] /IfModule WebAppConnection conn warpmyhost.mydomain:8008 WebAppDeploy cocoonconn/cocoon /VirtualHost I also modified the Cocoon sitemap.xmap to forward the processing to a sitemap outside of the Cocoon tree. This URL works: http://myhost.mydomain/cocoon/xml/foo * Apache correctly passes the /cocoon/xml/foo address to Tomcat which then passes it to Cocoon. Output is correct This URL http://myhost.mydomain/xml/foo is redirected to http://myhost.mydomain/cocoon/xml/foo and the user sees it in the browser. Not what I wanted. I tried the single line [PT] variation shown in the FAQ, and as indicated there, this does not work at all. Thoughts? Regards, --- Bob Bourdeau - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL rewriting solution in FAQ does not do the trick
Why not do this in $CATALINA_HOME/conf/server.xml: Context path= docBase=cocoon debug=0 reloadable=true/ Regards, Lajos Robert Bourdeau wrote: This is more of an Apache question than a Cocoon question, but hopefully someone will know what I'm doing wrong here. Setup: SPARC Solaris 2.7, Apache 1.3.24 w/mod_webapp (Warp), and Tomcat 4.0.1 Goal: Eliminate cocoon from the URL Constraints: Want all my custom content (XML, stylesheets, etc.) to be removed from the Cocoon tree so I can upgrade Cocoon separately. Must use Apache to receive request. URL mapping has to be done per virtual host. I looked at the FAQ, and followed the instructions. I rebuilt Apache with mod_rewrite enabled, then added the followed code to my httpd.conf: VirtualHost myhost.mydomain:80 ServerName myhost.mydomain DocumentRoot /myhost.mydomain/htmls IfModule mod_rewrite.c RewriteEngine on RewriteLog /var/adm/www/rewrite.log RewriteLogLevel 9 RewriteRule ^/xml /cocoon/xml/ [R] RewriteRule ^/xml(.*) /cocoon/xml$1 [R] /IfModule WebAppConnection conn warpmyhost.mydomain:8008 WebAppDeploy cocoonconn/cocoon /VirtualHost I also modified the Cocoon sitemap.xmap to forward the processing to a sitemap outside of the Cocoon tree. This URL works: http://myhost.mydomain/cocoon/xml/foo * Apache correctly passes the /cocoon/xml/foo address to Tomcat which then passes it to Cocoon. Output is correct This URL http://myhost.mydomain/xml/foo is redirected to http://myhost.mydomain/cocoon/xml/foo and the user sees it in the browser. Not what I wanted. I tried the single line [PT] variation shown in the FAQ, and as indicated there, this does not work at all. Thoughts? Regards, --- Bob Bourdeau - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cocoon training, consulting support galatea.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: URL rewriting solution in FAQ does not do the trick
Lajos, OTOH, the adding of this context will make the Tomcat doc and Tomcat home page unreacheable. There are ways around it (like the adding of /root and /tomcat-docs contexts), but replacing the default Tomcat behaviour doesn't seem to me such a good idea; though, it may be just fine for a production environment. In my opinion the use of mod_rewrite, ugly as it may be, is still the path of least resistance (it doesn't alter the behaviour of anything). Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: Lajos Moczar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 5:57 PM To: [EMAIL PROTECTED] Subject: Re: URL rewriting solution in FAQ does not do the trick Why not do this in $CATALINA_HOME/conf/server.xml: Context path= docBase=cocoon debug=0 reloadable=true/ Regards, Lajos Robert Bourdeau wrote: This is more of an Apache question than a Cocoon question, but hopefully someone will know what I'm doing wrong here. Setup: SPARC Solaris 2.7, Apache 1.3.24 w/mod_webapp (Warp), and Tomcat 4.0.1 Goal: Eliminate cocoon from the URL Constraints: Want all my custom content (XML, stylesheets, etc.) to be removed from the Cocoon tree so I can upgrade Cocoon separately. Must use Apache to receive request. URL mapping has to be done per virtual host. I looked at the FAQ, and followed the instructions. I rebuilt Apache with mod_rewrite enabled, then added the followed code to my httpd.conf: VirtualHostmyhost.mydomain:80 ServerNamemyhost.mydomain DocumentRoot /myhost.mydomain/htmls IfModule mod_rewrite.c RewriteEngine on RewriteLog /var/adm/www/rewrite.log RewriteLogLevel 9 RewriteRule ^/xml /cocoon/xml/ [R] RewriteRule ^/xml(.*) /cocoon/xml$1 [R] /IfModule WebAppConnection conn warpmyhost.mydomain:8008 WebAppDeploy cocoonconn/cocoon /VirtualHost I also modified the Cocoon sitemap.xmap to forward the processing to a sitemap outside of the Cocoon tree. This URL works: http://myhost.mydomain/cocoon/xml/foo * Apache correctly passes the /cocoon/xml/foo address to Tomcat which then passes it to Cocoon. Output is correct This URL http://myhost.mydomain/xml/foo is redirected to http://myhost.mydomain/cocoon/xml/foo and the user sees it in the browser. Not what I wanted. I tried the single line [PT] variation shown in the FAQ, and as indicated there, this does not work at all. Thoughts? Regards, --- Bob Bourdeau - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cocoon training, consulting support galatea.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL rewriting solution in FAQ does not do the trick
True, you are building stuff right out of the box and don't want to make configuration changes that might be overwritten when you reinstall or upgrade components. However, for production purposes, the Tomcat home and docs pages are oftentimes superfluous (just like Cocoon examples, Apache docs, etc.). At least I find them sperfluous, as do many of my clients. Hence, I typically strip off all included webapps, and make cocoon the ROOT context. Regards, Lajos Luca Morandini wrote: Lajos, OTOH, the adding of this context will make the Tomcat doc and Tomcat home page unreacheable. There are ways around it (like the adding of /root and /tomcat-docs contexts), but replacing the default Tomcat behaviour doesn't seem to me such a good idea; though, it may be just fine for a production environment. In my opinion the use of mod_rewrite, ugly as it may be, is still the path of least resistance (it doesn't alter the behaviour of anything). Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: Lajos Moczar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 5:57 PM To: [EMAIL PROTECTED] Subject: Re: URL rewriting solution in FAQ does not do the trick Why not do this in $CATALINA_HOME/conf/server.xml: Context path= docBase=cocoon debug=0 reloadable=true/ Regards, Lajos Robert Bourdeau wrote: This is more of an Apache question than a Cocoon question, but hopefully someone will know what I'm doing wrong here. Setup: SPARC Solaris 2.7, Apache 1.3.24 w/mod_webapp (Warp), and Tomcat 4.0.1 Goal: Eliminate cocoon from the URL Constraints: Want all my custom content (XML, stylesheets, etc.) to be removed from the Cocoon tree so I can upgrade Cocoon separately. Must use Apache to receive request. URL mapping has to be done per virtual host. I looked at the FAQ, and followed the instructions. I rebuilt Apache with mod_rewrite enabled, then added the followed code to my httpd.conf: VirtualHost myhost.mydomain:80 ServerName myhost.mydomain DocumentRoot /myhost.mydomain/htmls IfModule mod_rewrite.c RewriteEngine on RewriteLog /var/adm/www/rewrite.log RewriteLogLevel 9 RewriteRule ^/xml /cocoon/xml/ [R] RewriteRule ^/xml(.*) /cocoon/xml$1 [R] /IfModule WebAppConnection conn warpmyhost.mydomain:8008 WebAppDeploy cocoonconn/cocoon /VirtualHost I also modified the Cocoon sitemap.xmap to forward the processing to a sitemap outside of the Cocoon tree. This URL works: http://myhost.mydomain/cocoon/xml/foo * Apache correctly passes the /cocoon/xml/foo address to Tomcat which then passes it to Cocoon. Output is correct This URL http://myhost.mydomain/xml/foo is redirected to http://myhost.mydomain/cocoon/xml/foo and the user sees it in the browser. Not what I wanted. I tried the single line [PT] variation shown in the FAQ, and as indicated there, this does not work at all. Thoughts? Regards, --- Bob Bourdeau - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cocoon training, consulting support galatea.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- galatea.com Cocoon training, consulting support - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: URL rewriting solution in FAQ does not do the trick
From: Luca Morandini [mailto:[EMAIL PROTECTED]] Lajos, OTOH, the adding of this context will make the Tomcat doc and Tomcat home page unreacheable. $TOMCAT_HOME/bin/shutdown cd $TOMCAT_HOME/webapps mv ROOT tomcat mv cocoon ROOT $TOMCAT_HOME/bin/startup :) There are ways around it (like the adding of /root and /tomcat-docs contexts), but replacing the default Tomcat behaviour doesn't seem to me such a good idea; though, it may be just fine for a production environment. This context (ROOT) is == to the Apache's famous This host has Apache HTTP server installed, and does not have own web site developed yet. Please do not write Apache about this happy guy who managed to install Apache HTTP server and must be removed as soon as solution goes to QA, or even way before this. :) In my opinion the use of mod_rewrite, ugly as it may be, is still the path +1. It is ugly. of least resistance (it doesn't alter the behaviour of anything). -1. Why keep ugly and less performing solution while others exist? Vadim Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: Lajos Moczar [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 5:57 PM To: [EMAIL PROTECTED] Subject: Re: URL rewriting solution in FAQ does not do the trick Why not do this in $CATALINA_HOME/conf/server.xml: Context path= docBase=cocoon debug=0 reloadable=true/ Regards, Lajos Robert Bourdeau wrote: This is more of an Apache question than a Cocoon question, but hopefully someone will know what I'm doing wrong here. Setup: SPARC Solaris 2.7, Apache 1.3.24 w/mod_webapp (Warp), and Tomcat 4.0.1 Goal: Eliminate cocoon from the URL Constraints: Want all my custom content (XML, stylesheets, etc.) to be removed from the Cocoon tree so I can upgrade Cocoon separately. Must use Apache to receive request. URL mapping has to be done per virtual host. I looked at the FAQ, and followed the instructions. I rebuilt Apache with mod_rewrite enabled, then added the followed code to my httpd.conf: VirtualHost myhost.mydomain:80 ServerName myhost.mydomain DocumentRoot /myhost.mydomain/htmls IfModule mod_rewrite.c RewriteEngine on RewriteLog /var/adm/www/rewrite.log RewriteLogLevel 9 RewriteRule ^/xml /cocoon/xml/ [R] RewriteRule ^/xml(.*) /cocoon/xml$1 [R] /IfModule WebAppConnection conn warpmyhost.mydomain:8008 WebAppDeploy cocoonconn/cocoon /VirtualHost I also modified the Cocoon sitemap.xmap to forward the processing to a sitemap outside of the Cocoon tree. This URL works: http://myhost.mydomain/cocoon/xml/foo * Apache correctly passes the /cocoon/xml/foo address to Tomcat which then passes it to Cocoon. Output is correct This URL http://myhost.mydomain/xml/foo is redirected to http://myhost.mydomain/cocoon/xml/foo and the user sees it in the browser. Not what I wanted. I tried the single line [PT] variation shown in the FAQ, and as indicated there, this does not work at all. Thoughts? Regards, --- Bob Bourdeau -- Cocoon training, consulting support galatea.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: URL rewriting solution in FAQ does not do the trick
-1. Why keep ugly and less performing solution while others exist? because I don't like altering the behaviour of Tomcat, messing around with its own servlets: I may not be the only one using Tomcat on that machine :( Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URL rewriting solution in FAQ does not do the trick
This is more of an Apache question than a Cocoon question, but hopefully someone will know what I'm doing wrong here. Setup: SPARC Solaris 2.7, Apache 1.3.24 w/mod_webapp (Warp), and Tomcat 4.0.1 Goal: Eliminate cocoon from the URL Constraints: Want all my custom content (XML, stylesheets, etc.) to be removed from the Cocoon tree so I can upgrade Cocoon separately. Must use Apache to receive request. URL mapping has to be done per virtual host. I looked at the FAQ, and followed the instructions. I rebuilt Apache with mod_rewrite enabled, then added the followed code to my httpd.conf: VirtualHost myhost.mydomain:80 ServerName myhost.mydomain DocumentRoot /myhost.mydomain/htmls IfModule mod_rewrite.c RewriteEngine on RewriteLog /var/adm/www/rewrite.log RewriteLogLevel 9 RewriteRule ^/xml /cocoon/xml/ [R] RewriteRule ^/xml(.*) /cocoon/xml$1 [R] /IfModule WebAppConnection conn warpmyhost.mydomain:8008 WebAppDeploy cocoonconn/cocoon /VirtualHost I also modified the Cocoon sitemap.xmap to forward the processing to a sitemap outside of the Cocoon tree. This URL works: http://myhost.mydomain/cocoon/xml/foo * Apache correctly passes the /cocoon/xml/foo address to Tomcat which then passes it to Cocoon. Output is correct This URL http://myhost.mydomain/xml/foo is redirected to http://myhost.mydomain/cocoon/xml/foo and the user sees it in the browser. Not what I wanted. I tried the single line [PT] variation shown in the FAQ, and as indicated there, this does not work at all. This is what I use (apache 1.3.24, Tomcat 4.0.4): VirtualHost www.mydomain DocumentRoot /home/sites/www.mydomain RewriteEngine On RewriteRule ^/(.*)\.jsp$ /jsp/$1.jsp [R] RewriteRule ^/(.*)\.xml$ /xml/$1.xml [R] IfModule mod_webapp.c WebAppConnection netConnection warp www.mydomain:8008 WebAppDeploy Servlets netConnection /Servlet WebAppDeploy cocoon netConnection /xml WebAppDeploy jsp netConnection /jsp /IfModule /VirtualHost (I have similar entries, with different WebAppConnections, for the other virtual hosts). This way http://www.mydomain/test.xml gets redirected to http://www.mydomain/xml/test.xml which gets passed on to cocoon (Servlets and jsp references get passed on directly to Tomcat). Make sure that the tomcat server.xml entry has a connector for each virutal host in the Tomcat-Apache Service section, e.g.: Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 address=10.9.8.7 minProcessors=5 maxProcessors=75 enableLookups=true appBase=www.mydomain_apps acceptCount=10 debug=0/ -- Dr. Everett (Skip) Carter Phone: 831-641-0645 FAX: 831-641-0647 Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED] 1340 Munras Ave., Suite 314WWW: http://www.taygeta.com Monterey, CA. 93940 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: URL rewriting solution in FAQ does not do the trick
From: Luca Morandini [mailto:[EMAIL PROTECTED]] -1. Why keep ugly and less performing solution while others exist? because I don't like altering the behaviour of Tomcat, messing around with its own servlets: I may not be the only one using Tomcat on that machine :( Then, I suppose, that's not a production box but rather some kind of dev environment, where it is not necessary to have Apache at all (up to integration testing). But when you go into production, it's better to remove these docs (do you want your customers to see Yep, Tomcat *is* working on this machine!!! when they go to the root of your server? Yes, you can hide it by giving some CPU time to URL rewriting module :) Vadim Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: URL rewriting solution in FAQ does not do the trick
Vadim, just for the sake of a nice discussion about best practices in software development... 1) First thing I do starting a development is to set up a development environment equal to the production one: I don't want nasty suprises down the line 2) I don't like messing up the baae packages I use (Apache/IIS, Tomcat, Cocoon, Oracle/DB2, ...) I may not be the one maintaining them (I'm a consultant, not an employee) Anyway, maybe it's time I rewrite the FAQ on this one, inserting Lajos' method as well. Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 8:17 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: URL rewriting solution in FAQ does not do the trick From: Luca Morandini [mailto:[EMAIL PROTECTED]] -1. Why keep ugly and less performing solution while others exist? because I don't like altering the behaviour of Tomcat, messing around with its own servlets: I may not be the only one using Tomcat on that machine :( Then, I suppose, that's not a production box but rather some kind of dev environment, where it is not necessary to have Apache at all (up to integration testing). But when you go into production, it's better to remove these docs (do you want your customers to see Yep, Tomcat *is* working on this machine!!! when they go to the root of your server? Yes, you can hide it by giving some CPU time to URL rewriting module :) Vadim Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
