omcat passing requests to cocoon for docroot, but not
sub-directories?
Well a follow up to say I fixed the problem. As I suspected it was a
problem with Tomcat, not Cocoon.
Short backstory, basically we had an existing web application using
older version of Tomcat/Cocoon and this was part of the pr
Well a follow up to say I fixed the problem. As I suspected it was a
problem with Tomcat, not Cocoon.
Short backstory, basically we had an existing web application using
older version of Tomcat/Cocoon and this was part of the process of
updating and moving everything to a newer faster environment.
How about if you test something like:
or
and then try
http://test.domain/main/randomfilename.jhtml
mika
Jed kirjoitti:
Have done all of those things already.
- Jed
On 10/04/2008, Lehtonen, Mika <[EMAIL PROTECTED]> wrote:
Hi,
can't you just leave the mod_jk out of this
Hi Jed,
Jed schrieb:
> Hi Jeroen,
>
> Thanks for the suggestion. I did actually try that but it didn't solve it. :(
>
> The problem is that Tomcat still appears to NOT be passing any request
> for a *.jhtml document in the docroot/main folder to cocoon.
>
> As I said, when I ask for http://test
Have done all of those things already.
- Jed
On 10/04/2008, Lehtonen, Mika <[EMAIL PROTECTED]> wrote:
> Hi,
>
> can't you just leave the mod_jk out of this for now on and test directly
> with Tomcat e.g. configure it to listen port 8080. Another approach might be
> to leave Cocoon out and test s
Hi,
can't you just leave the mod_jk out of this for now on and test directly
with Tomcat e.g. configure it to listen port 8080. Another approach
might be to leave Cocoon out and test some static material through
mod_jk. That way you can assure that it is working properly.
mika
Jed kirjoitti
I know mod_jk is working because it's passing the request through to
Tomcat. Instead of trying to serve the *.jhtml file from Apache, it's
going to Tomcat which is then passing back it's *own* 404 message
rather than the default apache version.
I've got mod_jk in debug mod and looked at the output
Well then it must be your mod_jk configuration. I do not have a lot of
experience with that, since I normally use mod_rewrite or mod_proxy.
On the cocoon side the correct way to go is without the preceding "/", so
Should be
So somehow tomcat or apache does not know how to handle reques
Hi Jeroen,
Thanks for the suggestion. I did actually try that but it didn't solve it. :(
The problem is that Tomcat still appears to NOT be passing any request
for a *.jhtml document in the docroot/main folder to cocoon.
As I said, when I ask for http://test.domain/test.jhtml cocoon
recieves the
Yes you are correct here. Remove the "/" from the beginning. Also use a
relative source:
Use
instead of
Regards,
Jeroen
Rainer Pruy wrote:
Hi Jed,
you might try using (leaving out the "/").
I remember having experienced similar problem some tim ago.
Regards
Rainer
Jed schrieb:
Hi A
Hi Jed,
you might try using (leaving out the "/").
I remember having experienced similar problem some tim ago.
Regards
Rainer
Jed schrieb:
> Hi All,
>
> I'm a new Cocoon user and I've come across and I'm having a really
> bizarre problem at the moment which has stopped my site development in
>
Hi All,
I'm a new Cocoon user and I've come across and I'm having a really
bizarre problem at the moment which has stopped my site development in
it's tracks.
I've got Apache/Tomcat/Cocoon set-up and have got the Tomcat and
Cocoon samples running just fine. I've set-up a virtual server with
it's
12 matches
Mail list logo
