|
Q
|
We have a clustered load-balanced server configuration with browserhawk installed on all of our clustered servers. At the front end of these servers, we have a router which sends page requests to the least active server. This means
that a user's session bounces back and forth between servers by design.
The question is how this may affect detection such as disabled cookies, JavaScript, Flash, etc. I know that some of these functions issue redirects back to the calling page from the server to the client, and then back
to the server again. Is it a problem if the actual physical server sending the initial request and the server receiving the information back from the client are different?
|
|
A
|
Not a problem - BrowserHawk is specifically designed with this in mind. Therefore the server which generates the initial extended property check (say for disabled cookies) and the server that receives the results of the check can be two different servers and BrowserHawk will still provide you with accurate results.
However, if you are using the GetExtProperties default RequestType of 0, or the RequesetType of 1 (cookie-based) you must explictly set the CookieDomain property prior to calling GetExtPropertiesEx for this to work properly. Otherwise the results will be lost once the test completes.
See the CookieDomain property in the BrowserHawk documentation for more information on using this property.
|
