Last post May 04, 2011 08:06 AM by eddyuk
May 03, 2011 09:45 AM|eddyuk|LINK
I wonder abount other oppinions about idea I have in mind. Final purpose is to redirect user to URL as fast as possble.
Ways I were thinking about:
1. Create something.ashx file that will recieve destination url via url query parameter and then simple response.redirect.
I rather use ashx and not aspx to avoid page lifetime cycle.
2. A bit crazy idea create ashx with destination domain name (!) means for each domain there will be ashx file that will handle only dedicated
redirection. But when I give future thought, and list of destination url's will grow, there will be a lot of ashx files in directory... Won't it be
heavy for proccess pool?..
Would love to hear your oppinions or other suggestions better then mines =)
Thanks in advanced
May 04, 2011 05:10 AM|stevenlauwers22|LINK
Response.Redirect returns a message to the client to tell the browser it needs to go to the URL you specify. You might want to consider using Server.Transfer which goes to the URL without first returning to the client, but beware there are some disadvantages
to this approach.
May 04, 2011 07:17 AM|jerryjoseph|LINK
Redirecting using Server.Transfer willl be faster than your solutions using ashx.
So if you are looking for the fastest redirect then it is Server.Transfer.
May 04, 2011 08:06 AM|eddyuk|LINK
it can be ouside domain... thats why i need redirect. thanks