Hello; I have a website which has two request types per view:
1) Is an aspx page with a querystring.
2) Is a "file" which has a filename of the querystring from (1) base-64 encoded. This "file" is rewritten to page.aspx?query=<filename> by the LB machines.
A client will request (1), then (2). The problem is that both (1) and (2) need to be routed to the same application server.
The reasons for this setup are necessary, but difficult to explain, sorry. Given these requirements, we tried using IP-based affinity (our client doesn't respect cookie affinity). This worked until we were behind a CDN. Now the client IP is hidden, there are no client-based request headers, and so all requests are hitting the same server.
Ideally, I'd like to be able to hash both (1) and (2) to the same randomly chosen application server. This seems like it would require some base64 logic in the Querystring rule, but maybe not.
Any thoughts? Thanks!