Hi All
I setup a load balance by using Nginx, there have several Linux boxes
running PHP+MySQL as the backend servers, they’re all for Blog service.
-------±------±----±----±----±–
| | | | |
±-±-+ ±±+ ±±+ ±±+ ±±+
| LB1 | | A | | B | | C | | D |
±----+ ±–+ ±–+ ±–+ ±–+
Nginx several Blog servers
Assuming the domain name is blog.abc.com, when user sign in server A
with his own username and password, if he try to access blog.abc.com
again, it’s possible that his requests will be transferred to server B
or others, then I think this user will be asked for input his username
and password again on server B or others. So my question is how can I
configure Nginx to let this user access server A again when he access blog.abc.com until he sign out?
with his own username and password, if he try to access blog.abc.com
again, it’s possible that his requests will be transferred to server B
or others, then I think this user will be asked for input his username
and password again on server B or others. So my question is how can I
configure Nginx to let this user access server A again when he access blog.abc.com until he sign out?
Nginx have not this possibility yet.
A possible solution is to use haproxy[1] as upstream target and let
haproxy[1] make the cookie stickyness
Hi All
I setup a load balance by using Nginx, there have several Linux boxes
running PHP+MySQL as the backend servers, they’re all for Blog service.
It’s the “same” blog service?
and password again on server B or others. So my question is how can I
configure Nginx to let this user access server A again when he access blog.abc.com until he sign out?
Rewrite the blog application if this happens, since they are not
restful.
Assuming the domain name is blog.abc.com, when user sign in server A
I did something similar a while ago. The attached patch adds variables
for accessing cookies ($http_cookie_foo => “foo” cookie). You can use it
in conjunction with the Upstream Hash module:
I did something similar a while ago. The attached patch adds variables
for accessing cookies ($http_cookie_foo => “foo” cookie). You can use it
in conjunction with the Upstream Hash module:
I think you forgot to add the attachment
I tried using mod_userid and hash $uid_got, but unfortunately to no
avail
Your patch would be very useful to me.
I did something similar a while ago. The attached patch adds variables
for accessing cookies ($http_cookie_foo => “foo” cookie). You can use it
in conjunction with the Upstream Hash module:
I think you forgot to add the attachment
I tried using mod_userid and hash $uid_got, but unfortunately to no
avail
Your patch would be very useful to me.