Re4: [users@httpd] stickysession at mod_proxy_balancer

[dom <ap...@friibii.ch>]

dear oliver,

hmm.. that was i guessd as well at the beginning, so i added the cookie
[%{sessionkey}C] into the apache-log-file, and it looks exactely like it have
to [12345678.A_]! :-(

strange is that when i access the balancing module (the summary where all the
members are shown, etc..) on stickysession is no entry, the route is shown..
when i manually add sessionkey to 'stickysession' it's shown but same
funtionality..

i'm going stupid soon.. ;-)

thanks
dom

> Hi dom,
>
> so than it seems that the definitions which you had in your apache 
> configuration don't match your session cookie
>
> Can you use "tamper data"  
> https://addons.mozilla.org/extensions/moreinfo.php?id=966&application=firefox 
> <https://addons.mozilla.org/extensions/moreinfo.php?id=966&application=firefox>
> or iehttpheaders to see whar you have in your headers sent by the 
> server when he sends you the cookie [the line sith "set-cookie"] . 
> Upon this set-cookie your Browser should send back every time a 
> headerline beginning with "cookie".
> If this is the case than the cookie should look like
> 12345678.A_ oder 12345678.B_ . Otherwise you have to change your 
> configuration
>
> If you don't want to run in a timeout or if you have a firewall 
> inbetween the apache and the backend web server than you can add 
> "keepalive=on" behind the route.
>
> bye
>
> Oliver
>
> ________________________________
>
> Von: dom [mailto:apache@friibii.ch]
> Gesendet: Mi 18.01.2006 12:27
> An: users@httpd.apache.org
> Cc: Schaudt, Oliver
> Betreff: Re: [users@httpd] stickysession at mod_proxy_balancer
>
>
>
> Hi Oliver,
>
> 1. no, i don't.. thats the strange thing.. just see in the accesslog:
> [debug] mod_proxy_balancer.c(41): proxy: BALANCER: canonicalising URL
> //produrl/site
> [debug] mod_proxy_balancer.c(803): proxy: Entering byrequests for BALANCER
> (balancer://prod)
> [debug] mod_proxy_balancer.c(396): proxy: BALANCER (balancer://prod) worker
> (http://192.168.1.1:8001 <http://192.168.1.1:8001/> ) rewritten to 
> http://192.168.1.1:8001/site
> [debug] mod_proxy.c(736): Running scheme balancer handler (attempt 0)
>
> 2. don't really understand your question. my 'backendservers' produce 
> a cookie
> with teh attribute 'sessionkey' and use this for the own
> sessiondeclaration, so
> i thought to use that one. i (the webserver) just added ".A_" at the
> end of the
> sessionkey for identify the 'route' to apache, but i guess thats not the only
> thing i need to do? i can produce every cookie-attribute you like, thats not
> the problem.. whats jvmroute? i'm not using tomcat, we use a self written
> webserver..
>
> i thought it should be easy: a have allready a sessionkey, so thats 
> nice. then
> the backendwebserver now which server he is, so he set another attribute, and
> add this to the sessionkey (sessionkey.route) and this route is
> definied on the
> BalanceMember.. but i guess i missunderstand the topc.. :-(
>
> bye
> dom
>
> Quoting Oliver.Schaudt@unilog.de:
>
>> Hi dom,
>>
>> 1. Do you see some lines like "proxy: BALANCER: Found value
>> 12721798.A_ for stickysession sessionkey" in the "error_log" ?
>> 2.Do you have set your session-identifier nameinside your servers
>> behind Apache to "sessionkey" and the route alias jvmroute to your
>> "A_" and "B_" ? If not than it won't work.
>>
>> Bye
>>
>> Oliver
>>
>> ________________________________
>>
>> Von: dom [mailto:apache@friibii.ch]
>> Gesendet: Di 17.01.2006 16:23
>> An: users@httpd.apache.org
>> Betreff: [users@httpd] stickysession at mod_proxy_balancer
>>
>>
>>
>> hi,
>>
>> i'm using apache 2.2 because of the balancing module, but i can't
>> figure out why
>> the 'stickyness' doesn't work.
>>
>>
>> -snip-
>> LogLevel debug
>> ProxyPass / balancer://prod/ stickysession=sessionkey nofailover=On
>>  <Proxy balancer://prod>
>>   BalancerMember http://192.168.1.1:8001 <http://192.168.1.1:8001/>  
>> <http://192.168.1.1:8001/>  route=A_
>>   BalancerMember http://192.168.1.2:8001 <http://192.168.1.2:8001/>  
>> <http://192.168.1.2:8001/>  route=B_
>>  </VirtualHost>
>> -snip-
>>
>> the sessionkey-coockie is set to something like 12721798.A_
>>
>> after a few clicks (depends from 2 to 15) i get connectet to the
>> second Member,
>> but don't see why! any ideas?
>>
>> when i have a look at the logfile, i never see some information about the
>> coockie or so.. :-(
>>
>> thanks in advance
>> dom
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>
>




---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org