Home/ Questions/Q 7811381
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T04:08:30+00:00

Is there a way to save the querystring ids after the page load? the

  • 0

Is there a way to save the querystring ids after the page load? the reason why i am looking is that …i should be back and forth with pages and more importantly if the user try to manupluate the ids then it should not effect the result of my page since i will be reading the Ids not from querystring but from some save prop or something like that.

for an example: let says the page loads very first time… i have this url:

http://www.somesite.com/Shop/Product/Detail.aspx?ProductId=100

and if the user try to modify the querystirng and re-load the page then the page_load should not read from querystring rather from saved prop or something???

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This would not work since it’s against the very basic nature of Internet. Internet is stateless.

    Everytime user changes the querystring, it will be treated as a new Url, storing the parameters will be of no use. Page.IsPostback won’t work either since every Url change will be a first hit.

    Saying that, you can still work around it,

    1. With every Url, you can pass a unique identifier (like a GUID.)

    2. As soon as page hits, you can save parameters in session and work with them and use the Guid to map the two requests.

    But the problem remains here, if the user changes that Guid then again it will be treated as a new request. You can go one step ahead and start saving that GUID to make sure that only system generated GUIDs are handled but overall it will just make your system complex.

    My guess is that you might be looking at a wrong solution for your problem. If you can share your actual aim then we might be able to recommend you something more tangible.

    • 0