Using URIs to Create Client-specific Look'n'feel

Question

There are customers who want to customize the brand of my product, although I can agree to manage and maintain the site. I have seen people do this by creating specific URIs for clients, such as:

    <customer1>.WebSite.com
    <customer2>.WebSite.com
    <customer3>.WebSite.com
    ...

Each customerX identifier is obviously used to load the CSS / HTML composition that best suits the requirements of the client.

How to do it in ASP.NET? Any serious issues I should know about? Is it difficult to maintain such an offer if clients are highly dependent on JS and CSS hackers?

Answer 1

, , , .

, DNS DNS-, Request httpmodule, - , CSS.

HTTPS , , .

Answer 2

JS CSS-? CSS JS .

Answer 3

, :

• /, / .

• , .

• When a client wants to configure it, copy it to your site. Change the links on the client’s website to their copy of the resource.

---

One thing you have to keep track of is that the client is twisting its version and malicious file changes.