Sep 17, 2015 07:15 AM|Ben Daouda|LINK
thanks for the response
May be i need to clarify few others things .. i dont want to use any sort of authentication since we are using the app to share data with external partners and i dont want end users to be forced to register to get access to data. However i want to restrict
the scope of data that will be made available to end users accessing the web app from internet by using an additional parameter in the stored proc calls. So far the only way for me to know the origin of the http request i mean internet or intranet is to rely
on HttpContext.Current.Request.Url but it does not help to differentiate since the result is the same whether you use public link (www.appname.com) ) or private link (htttp://computername), it always gives the latter. We used
reverse proxy to publish the web app in internet. I am thinking about a solution that will read the current browser link. may be there are some others better alternatives out there. Getting end users ip as suggested earlier was not that helpfull because the
result does not always lcome in ipv4 format.