ApplicationOverride with apache reverse proxy and different configurations per customer

[Peter Schober]

* Micky Williamson <mwilliamson at silasg.com> [2016-07-12 03:57]:
> Our issue about paths versus virtual hosts, In general this is going
> to be forward facing to many customers, under one product name, say:
> myproduct.company.com  then each customer would be /cust1 /cust2 on
> the end of the URL.   (the reason for the /cust1 /cust2 urls is that
> the backend application is not multi tenant capable (bad design I
> know, I didn't write it).  To do virtual hosts, you would have to
> have cust1product.company.com cust2product.company.com (AFAIK) and
> the company has decided that from a branding perspective, they don't
> want to do that...

How about cust<n>.product.company.com, then?
Or cust<n>.company.com/product/ ?

Those would still isolate customers with vhosts and are maybe less
ugly than cust1product.company.com?

Just a thought.
-peter