Turner, John wrote:
Hello -
We have an app running on 4.1.12.
In stand-alone mode, this URL works perfectly:
http://some.server.com:8080/myApp
http://some.server.com:8080 also works perfectly (myApp is the default app)
With Apache (2.0.43), using JK, the GIF images on the page show as
Just a loosely cupled bunch of questions/remarks.
Have you configured apache to forward all request to tomcat
or yust /servlet/* and *.jsp ?
To isolate the problem you could create a static page that
contains the same link.
With this page try it with mod_jk enabled/disabled to
see if you can
Thanks for the reply.
I think I have narrowed down what the issue is, but I'm at a loss on how to
resolve it. On the very first request, the image link sent to the browser
is this:
http://some.server.com/myApp/images/A2_incent.jpg;jsessionid=AF447A2112DDC43
E0745C06EB82623D0
However, if I
Thanks for the reply.
Apache is configured thusly:
JkMount /myApp/*.do ajp13
JkMount /myApp/*.jsp ajp13
It happens for every session, I can reproduce the behavior at will.
John
-Original Message-
From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20,
Syntaktically that's correct.
This is the way the session id is encoded in url's if no
cookie is there. For requests that are forwarded to tomcat
that's OK as tomcat knows how to deal with that.
But why is the url encoded at all ?
Do you call response.encodeUrl() on images ?
-Original
Hello -
We have an app running on 4.1.12.
In stand-alone mode, this URL works perfectly:
http://some.server.com:8080/myApp
http://some.server.com:8080 also works perfectly (myApp is the default app)
With Apache (2.0.43), using JK, the GIF images on the page show as broken
links the first
