Greetings all, Most web sites will lose your POST data if your session times out or you clear your cookies before issugin a POST request. They will direct you to a login prompt and then redirect you to the original URL without any regard for the post data that you sent when you timed out or lost your cookies.
This is an approach I came up with to avoid this: http://www.dotnetjunkies.com/WebLog/joshuagough/archive/2006/05/17/138522.aspx I'm migrating an existing asp system that provides this functionality. In asp it's quite simple and similar to this but of course does not involve "server side events" so there's no need to massage the request input stream. I was wondering if anyone knew of any alternatives or possible pitfalls of this httpModule approach. I already have thought of a couple potential problems (like avoiding certain pages or even certain fields from getting stored in the snapshot) One other thing I'm not sure about would be authentication failures and how to work with controls to display feedback. If the "event handler" is actuall y taking place in the module, then if authentication does fail, perhaps the post payload could just contain the error message in the form of a serialiazed asp:Login control with the properties of a FailureText property filled out. This way when the page loads, it looks as if everything took place in the page code, and the user can issue their uid / pwd again. No matter how many times they fail, the previous operations payload continues to get reposted within the __PAGESNAPSHOT until they actually succeed, and then the original request is decoded and posted.. Looking forward to opinions, Thank you Josh =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
