Scott_McCool_11
Dec 14, 2006Nimbostratus
Feasibility/examples: pseudo-QoS based on header
As we work to add capacity to our website, one of the things we'd like to do is ensure that paying customers receive the best possible experience (at the expense of "public" users if need be).
We've made basic steps in this regard by limiting spiders to a pool made up of a subset of our nodes, etc but we'd like to go further.
I can identify paying customers based on a custom HTTP header being added by our content delivery network, and sometimes by authorization data in the headers. What I'd like to do is take X servers, create a pool of all X to which "paying customers" are sent, a pool containing a subset of X for all other visitors, and an even smaller pool for spiders.
Does anyone have examples or a high level overview of how they've solved a similar problem? The custom HTTP header I refer to would be a source IP address that is added to every request, but I'd want to match to a particular list/range....
Is this feasible?