Multiview and browser back button

[Liming]

Hi,

I have a multiview (with 10 views inside). Now on View2, I ask the
user to uplaod a file and click Save to go to View3 and once they get
to view3? If the user hits my "previous" button, View2 needs to display
the filename of the uplaoded file.

Here is the problem.

1. In Firefox 1.5, in view3, if the user clicks "browser back" instead
of my "preivious" button, it'll retrieve a cached version (so my code
to redisplay the uploaded file name was not executed at all)

2. In IE 6.0, if the user clicks "browser" back, it simply says, the
page content is expired. Nothing gets displayed.

I played around with the
<%@OutputCache Duration="1" VaryByParam="None" %>

didn't work and then
Response.Cache.SetCacheability(HttpCacheability.NoCache)

that didn't work either.


What's going on? Thanks

Liming

 

[CMM]

I would launch that wizard in a separate window and turn off the toolbars.
window.open('mypage.aspx', '',
'toolbar=no,menubar=no,resizable=yes,scrollbars=yes,location=no,width=600,height=450');

There's no controlling what things a browser does with the History Page/Fwd.

 

[Joerg Jooss]

Thus wrote Liming,

Hi,

I have a multiview (with 10 views inside). Now on View2, I ask the
user to uplaod a file and click Save to go to View3 and once they get
to view3? If the user hits my "previous" button, View2 needs to
display the filename of the uplaoded file.

Here is the problem.

1. In Firefox 1.5, in view3, if the user clicks "browser back" instead
of my "preivious" button, it'll retrieve a cached version (so my code
to redisplay the uploaded file name was not executed at all)

2. In IE 6.0, if the user clicks "browser" back, it simply says, the
page content is expired. Nothing gets displayed.

I played around with the
<%@OutputCache Duration="1" VaryByParam="None" %>
didn't work and then
Response.Cache.SetCacheability(HttpCacheability.NoCache)
that didn't work either.

What's going on? Thanks

There's no guarantee that HTTP Cache-Control headers have any influence on
a browser's navigation controls. IE behaves like this, earlier versions of
Mozilla did, but Firefox doesn't -- and that's fully in line with the HTTP
1.1 spec.

You should provide an application specifc "back" link or button and make
sure your application doesn't fall apart if a user uses the browser's back
button and sends a potentially harmful request afterwards.

Cheers,