If you ever encountered this error in FireFox, it is because of the caching issue. See if you have any
response headers added to your code and remove the unnecessary ones. Response.SetCache.NoStore() also works. Overall, this is a firefox bug.
asp net forum link to problem
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment