I just realized something :( With HTTPRedirectToName, if the
redirected-to server dies, all users that bookmarked it will not be able
to access it. Duh. Unless I use fake for all my servers, or use some
other IP address failover method.
Oh well, I guess I will have to wait for Theo to come up with a way to
do half-proxying so I can be satisfied with the performance scaling :)
Dejan
Dejan Macesic wrote:
> (snip)
> The major problem is cookies. Some browsers (like mine) have "security"
> settings which prevent setting cookies through entire domains
> (*.mydomain.com), or setting cookies with a domain which is different to
> the current ServerName. This can break some applications. I haven't
> tackled this yet, but I'm working on it. Has anyone done this?
>
redirected-to server dies, all users that bookmarked it will not be able
to access it. Duh. Unless I use fake for all my servers, or use some
other IP address failover method.
Oh well, I guess I will have to wait for Theo to come up with a way to
do half-proxying so I can be satisfied with the performance scaling :)
Dejan
Dejan Macesic wrote:
> (snip)
> The major problem is cookies. Some browsers (like mine) have "security"
> settings which prevent setting cookies through entire domains
> (*.mydomain.com), or setting cookies with a domain which is different to
> the current ServerName. This can break some applications. I haven't
> tackled this yet, but I'm working on it. Has anyone done this?
>