Hello,
I am using HttpServletRequest.login to authenticate users on an ajax call.
This is working fine and the relevant realm is queried. However, on
subsequent requests, I have quite often the remote user being null despite
having the correct JSESSION cookie set from the login call.
This is not
Thanks again Rainer for guiding me toward the core/gdb/stacktrace approach.
After managing to get a meaningfull stacktrace (using gdb httpd core_file)
it was easy to see that the problem was NOT in mod_jk but in another
module (mod_auth_cas). I'll report this problem to them.
Best regards,
Nico
>
> Your test JSP works fine for me with Apache httpd 2.2.6 and mod_jk
> 1.2.25 on Solaris. Since your jk log file ends very early in the request
> processing, the tomcat version should not matter (I used 5.5).
>
> I would guess, that something with your build is broken. It would also
> help, if
I forgot to mention that the request is sent over https.
The https is handled by apache httpd. I am not sure If this has an impact
as it would be difficult for me to test it under http.
Cheers
Nicolas
-
To start a new topic,
Thank you Rainer for taking the time to answer. My comments are below.
>
> Not a known problem. You can increase log level via "JkLogLevel debug".
> There should be a line containing "service" or "Service", which includes
> the URI) we send forward to Tomcat.
>
> The log will also show you, i
Hello all,
I have apache 2.2 in front of tomcat 6.0.13 and I use mod_jk (1.2.25)
as the connector.
It seems that whenever a form containing a question mark at the end of
the form action parameter is posted, mod_jk is dying silently (but recover)
(The resulting url is something like that /mysit
Hello all,
I am having some difficulties to setup cactus tests using
tomcat > 5.5.20 (Everything works fine with 5.5.20).
I am using form authentication in cactus tests (as described
on the cactus web site). When I look at the generated request,
I get the authentication layer called with all t
