Comments by Gaurav Aroraa (Top 15 by date)

Good one

There are lot of articles and blog posts in CodeProject, you can refer to those

@AlFarooqueShubho - we found one another way to do this. I will be posted here. In between can you please post MSDN link, you mentioned.

It will take several days to prepare it. Because, I dont wnat editors to spend much time for editing on my articles :). I will comment here as soon as it get published (y)

We have found another way, I will be posting the same as an article so, others can also get benefited.

Great stuff man! It will definitely save my hundred hours (y)

Thanks Maciej - this is a good solution but unfortunately, its not working in our scenario. I will find-out why? Between, I am accepting your solution :)

laterally, I noticed there is no good solution available for this. I accepted your answer

Actually main issue is I used both urlreferrer and HTTP_REFERRER to detect incoming user urls. Which is working fine in local and test environment but its not working in production environment. All environments have same configuration and securities.

eg. on site abc.com there is a link which send user to site xyz.com now in the default landing page of xyz.com we are checking the incoming url which is abc.com in this case by using above and facing problem in production environment

Sorry I did not agree with you the same contains value when user coming from outside current application. I wrote its working fine in locally but the problem is on production.
Please check this : http://stackoverflow.com/questions/3524954/how-to-validate-incoming-urls

I know the querystring technique but its hard to change each and evrylink on any application if the querystring value will change in future