Forum Discussion
AltostratusMasking URL from diferent domains user autentication.
MVPHi,
Your question is not very clear and but in general you can mask an URL based on conditions, for example:
- If a client comes (or does not come) from predefined subnet then block access to url /xyz
Without more knwoledge of your app, it's difficult to give you suggestions, however you would better challenge the devs to build a good design of your app giving each client a dedicated endpoint, folders ...etc or have a single login page that can differentiate between clients giving them authorizations accordingly
lavila85Thank you guys for your time!.
Let me explain it in more detail.
We have a single website published on one IIS server called Q.
Client 1: Enter by URL: www.abc.com/login.aspx
Internal application path map: Qserverpath\clientfolder1\login.aspx
Client 2: Enter by URL: www.abc.com/subsite2/login.aspx
Internal application path map: Qserverpath\clientfolder2\login.aspx
Need:
Let client 2 enter its internal path but from the domain www.xyz.com
In other words hide the www.abc.com domain and replace it with www.xyz.com and map internal folder path: Qserverpath\clientfolder2\login.aspxThanks a lot!
- Amine_Kadimi
I second Paulius, just google for IIS hosting multiple sites by host header. F5 by itself cannot tell the backend server what folder to choose other than by an intermediary mean using HTTP (e.g. host header), IIS then chooses the folder accordingly
