asp.net - Which One is More Secure between Response.Redirect or Server.Transfer on the same server -

i have been reading these 2 functions , considering pick 1 more secure. want use server.transfer because executes @ server side in sense. better use?

server.transfer("myurl.aspx?id=1"); 

or

response.redirect("myurl.aspx?id=2"); 

update:

my question based on client side data security comes previous page rather url change.

tl;dr: neither server.transfer or response.redirect offers security advantages on other. recommend not using server.transfer @ all, anti-pattern of modern http/web resource base paradigms, further explanation on below. use response.redirect , focus on authorization/identity security concerns.

---

neither offers more security other. server/endpoint still allows http/https requests, request can sent server malicious client.

you should prefer response.redirect on server.transfer. server.transfer asp.net web forms "code smell". asp.net web forms has never respected http, restful, stateless, resource request web paradigms, the web built on, obviously.

server.transfer old method. server.transfer maintains original url in browser. can streamline data entry wizards, make confusion when debugging.

maintaining original url perfect example of asp.net web forms doing wants, making life easier in short term impacting maintainability of software in long term. maintaining original url perfect example of going against grain of http/web protocols. prevents user sharing resource url. and, if plan on url never being shared, there 1 use case still helpful user/system/exception handling able share url , provide correct place/resource user on, @ time of error or issue or user question, customer service/troubleshooting/debugging better serve user/customer/client.

server.transfer example of shortcut, has no security advantages, server/endpoints exposed on port 80 client requests whether responding different resource (server.transfer) or telling client redirect (response.redirect) , request resource.

regarding "skipping" round trip advantage of server.transfer on response.redirect, small benefit considering server.transfer web anti-pattern explained above. guides developers less elegant web systems architecture rather well.

regarding second parameter of server.transfer, perserveform, setting perserveform true maintain form , query string , still available next page sending user not advantageous enough warrant use because impacts long term maintainability of web application.

perserveform anti-pattern stateless, restful, resource based modern web applications/paradigms have been discussing above. if need maintain form state, across requests, should done on client local storage, not responsibility of server maintain state each client. perserveform yet example of asp.net web forms, trying make things easier developer in short term making code overly complex , difficult maintain , debug in long term.