Question 1
Originally, we had a big "router" page to which all forms submitted, and the router page had to determine which page the logic had come from.
We used Request.ServerVariables("HTTP_REFERRER"
and stripped everything before the last "/" which worked fine, except that a few of our customers had problems with that because of their company's firewalls. I understand that due to this problem, it is not advisable to use HTTP_REFERRER. I reckon I can use PATH_INFO instead of this, can anyone see any unforseen problems with this?
Question 2
We are going to have one physical site (in IIS) but it will be accessed from different URLs, to give us 2 or more conceptual sites. Then we will present the site with different branding (colours, logos etc), depending on what URL the user came from.
I have not set up a URL, and am using the IP address to enter the site at present. With this set-up, request.Servervariables("SERVER_NAME"
gives me the correct URL, ie the IP addy. Will this still work when I have a friendly URL assigned to each IP address? eg if I make "elite.mycompany.co.uk" = 10.xx.xx.160, and enter the site using the friendly URL, will Server_name return "elite.mycompany.co.uk"?
Many thanks for your help with this,
Lesley
Originally, we had a big "router" page to which all forms submitted, and the router page had to determine which page the logic had come from.
We used Request.ServerVariables("HTTP_REFERRER"
Question 2
We are going to have one physical site (in IIS) but it will be accessed from different URLs, to give us 2 or more conceptual sites. Then we will present the site with different branding (colours, logos etc), depending on what URL the user came from.
I have not set up a URL, and am using the IP address to enter the site at present. With this set-up, request.Servervariables("SERVER_NAME"
Many thanks for your help with this,
Lesley