You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mir S Islam <mi...@mindspring.net> on 2000/04/09 19:52:03 UTC

virtualhost

Hi, I have cocoon 1.7 installed on a linux machine. Everything works
fine. Cocoon intercepts xml file requests and processes themfine. But I
get an error file not found:
java.io.FileNotFoundException: /usr/local/apache/htdocs/hello-page.xml

When calling the page with virtualhost
http://vhost.host.com/hello-page.xml. Ofcourse, my vhost docroot is not
(/usr/local/apache/htdocs) where cocoon was looking for the requested
file.
However it works fine if I call
http://main.host.com/~vhostid/hello-page.xml
How can I get this to work for virtual hosts ? Thanks a lot developer
folks for this awsome product.

Mir


Cocoon2 installation with Tomcat

Posted by Johann Romefort <ro...@club-internet.fr>.
Can anyone tell me how to get Cocoon2 working
on Tomcat? I tried to follow Cocoon1 Installation
process just changing cocoon.properties with
cocoon.xconf but without success.

Another thing I'd like to know, concerns the size
of cocoon.jar file. I compile from the cvs, and the
jar file is only 110 ko (half size than Cocoon1). 
Is it normal?

Regards,

Johann


Re: virtualhost

Posted by Ed Knutson <ed...@webcombo.net>.
On Sun, 09 Apr 2000, Mir S Islam wrote:
> Hi, I have cocoon 1.7 installed on a linux machine. Everything works
> fine. Cocoon intercepts xml file requests and processes themfine. But I
> get an error file not found:
> java.io.FileNotFoundException: /usr/local/apache/htdocs/hello-page.xml

Do you by any chance have mod_rewrite on that server?  I have found that Cocoon
does not receive requests for any virtual hosts that have the RewriteEngine on,
regardless of what order the modules are compiled in. This appears to be a
mod_jserv or mod_rewrite issue, not Cocoon.  It may even be how Apache handles
the Action and AddHandler directives.

The solution is to use rewrite to redirect the requests to a vhost that does
not have it enabled.

Also, I have noticed that Apache web + Tomcat doesn't handle vhosts well,
either.  It will look for the requested file in the base server document root,
although images and the like that appear on that page are handled correctly (ie
are retrieved from the vhost docroot).  Thus, I would get the server root index
page with broken images (it was looking for them in the vhost directory).  I
never got that to work----but it works with the JServ 1.1 servlet engine just
fine.

-ed