> > 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.
>
> Hmmm, sounds a bit confusing. You'll need either working URL encoding
or
> working cookies. You can support both at the same time, but either of
it
> will suffice to implement session stickyness. mod_jk will look at the
> URL, searching for the ";jsessionid=..." as well as looking for a
> JSESSIONID cookie.
I would rather stick with cookies and forget about URL encoding, but
some devices just don't support cookies or have them disabled and for
our websites to work the requests to the images have to hit the same
server as the ones to the content page, that had the image links
included.
> If you want to track, in which cases the browsers suport 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 by adding
> %{JSESSIONID}C to the LogFormat, you can log the JSESSIONID cookie
send.
> By adding %{Set-Cookie}o you can log, whenever your server sets a new
> cookie.
That sounds very interesting, thanks! I will try this first thing in the
morning.
> You are aware of the fact, taht supporting session stickyness with
> mod_jk neeeds
>
> - an individual jvmRoute set in server.xml for each node
Check.
> - a loadbalancing worker defined for mod_jk, with one ajp member for
> each node, the name of the member equal to the jvmRoute (or at least
the
> route attribute set to that).
Check.
:-)
Greetings,
Timo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
