Re: mod_jk and session stickyness of images requests

2009-12-15 Thread Rainer Jung
On 15.12.2009 14:36, Kockert, Timo wrote: Thanks for all your answers so far! I'm still trying to figure out the problem but there are also some other things I need to take care of. Just to make it clear, here is a summary of my problem and what was suggested so far: - We have a webapp that s

Re: mod_jk and session stickyness of images requests

2009-12-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rainer, On 12/12/2009 10:46 AM, Rainer Jung wrote: > If you want to track, in which cases the browsers support what, you can > use the Apache access log. The URL is part of it, so you can see, > whether the session id was part of the request URL, and

Re: mod_jk and session stickyness of images requests

2009-12-12 Thread Rainer Jung
On 11.12.2009 18:38, Kockert, Timo wrote: We are using Cocoon and its EncodeUrlTransformer to do the session ID encoding: transformer.pool-max}" src="org.apache.cocoon.transformation.EncodeURLTransformer"> .*/@href=|.*/@action=|frame/@src=|img/@src=|input/@src= nonexistinght

Re: mod_jk and session stickyness of images requests

2009-12-11 Thread Len Popp
On Fri, Dec 11, 2009 at 12:38, Kockert, Timo wrote: > Just to clarify: I know the EncodeUrlTransformer does the > encoding for me. The problem seems to be that some > devices do not send session ID cookies with image > requests. Do you know what type of devices they are? Your log file may contain

Re: mod_jk and session stickyness of images requests

2009-12-11 Thread André Warnier
Kockert, Timo wrote: Hello everyone, first time posting to this list, so please don't be too hard with me ;-) We have a problem with the session stickyness of mod_jk in the context of image requests. First of all, here is our setup: 3 servers running Tomcat 5.5.x with AJP connector 2 servers r

Re: mod_jk and session stickyness of images requests

2009-12-11 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo, On 12/11/2009 10:27 AM, Kockert, Timo wrote: > first time posting to this list, so please don't be too hard with me ;-) Welcome to the list. Hey, you posted your relevant environment details, a clear description of your problem, and admitted th