There are many different setups, some simple and quick, some more advanced or focused on security, etc... so there isn't one general answer.
Quote:
Originally Posted by youngblood
The whitelabel server would have a virtual host listening on * (or aliased to *) and as such would accept all incoming requests from any domain and serve back the content on that WL server. But how does the WL server distinguish what which WL profile to send back to domain abc.com? Is there some sort of marker somewhere in that system which can identify all this?
|
In most cases, here is how they would know what white-label to load:
All requests use the same DocumentRoot and thus load the same files.
The included config file would determine the whitelabel based on domain name (as an example).
This variable is then used wherever it needs to generate or fetch content uniquely to that whitelabel (example in database queries, loading template sets, whatever).
Another idea is, yes, they very well could create a different virtualhost and documentroot per white label and automatically rewrite their virtualhost file when new white labels are generated, etc... for almost all cases though this is pretty inefficient.
Hope that helps you get started
