[WWdevel] webwork page caching

[P G. L. <gl...@um...>]

Hi all,

Watching some of our gateway testing, the following occurred to me: it 
would be good to avoid students being able to use the browser's "back" 
button to navigate.  And then I thought that this should be a desirable 
state of affairs in general.  Because WeBWorK pages contain state data, we 
don't really want people going back to previous pages.  I use this 
occasionally when I'm working as a course administrator, but on student 
pages I think it's something we don't want happening.

Would it make sense to add a 'no-cache' command to the header of all 
WeBWorK pages, so that it would force the browser to go back to the server 
to get each new page?

Thanks,
Gavin

-- 
P. Gavin LaRose, Ph.D.  Program Manager (Instructional Tech.)
Math Dept., University of Michigan
gl...@um...                        "There's no use in trying," [Alice]
734.764.6454                             said. "One Can't believe impossible
http://www.math.lsa.umich.edu/~glarose/  things." "I daresay you haven't had
                                          much practice," said the Queen.
                                                               - Lewis Carrol