Hi Peter,
As Bruce has suggested, one way to prevent this behavior is disable client
output cache in your page , thus whenever you click back button at client
browwer after a postback, it should display the expired page screen.
Also, another means you can consider is manually use Response.Redirect to
relocate the page to the current location. e.g.
============
#postback handler
{
//after finishing work
Response.Redirect(the page want to display);
}
=============
Also, this can help prevent resubmit the page when user click refresh
button.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Steven Cheng[MSFT] - 13 Jun 2007 16:22 GMT
Hi Peter,
Have you got any progress on this issue or does the suggestion in previous
messages help some? If there is anything else we can help, please feel free
to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.