I'm a little rusty on my HTTP, but I don't think that hitting the "back" button always gets things from the browser's cache - specifically, I'm thinking about the "Expires" and the "Cache-Control" HTTP response headers that can be sent along with the original page: e.g. if the server sets the "no-cache" option on Cache-Control or sets an Expires date that's in the past, then the browser shouldn't use a cached page.
I'm a newsbie when it comes to JSF, but does JSF not set these headers? In theory, this would solve the synchronization issue that is being mentioned: when the <back> button is hit, the browser should go to the server to re-fetch the page; JSF should be able to synchronize off that request, no? But maybe my memory on the caching stuff is a bit stale...can't remember if all browsers implemented it to spec. Hope this helps, tom -----Original Message----- From: Heath Borders-Wing [mailto:[EMAIL PROTECTED] Sent: Sunday, November 14, 2004 2:27 PM To: MyFaces Discussion Subject: Re: Back Button problems I don't think there is a way you coudl do this with javascript because when you hit the back button you aren't talking with the server at all, you are just going through the browser's cache. On Sun, 14 Nov 2004 08:45:08 -0700, Arinaya <[EMAIL PROTECTED]> wrote: > Ok that makes sense. > But is there any way to force JSF to refresh the View when a page is > loaded in the browser? > > Or is it possible to send a request automatically on page load if the > View is not synchronized with the current page? > > I think I could use javascript to do a form submit on page load, but > how would I check the current JSF View using javascript? Is it > possible? > > Thanks > > > > > -----Original Message----- > > From: Heath Borders-Wing [mailto:[EMAIL PROTECTED] > > Sent: Sunday, November 14, 2004 8:35 AM > > To: MyFaces Discussion > > Subject: Re: Back Button problems > > > > I tried the same thing. > > > > I don't know why client side state saving was throwing a > > NotSerializableException, but I know why you have to submit twice. > > > > Let's say you have two pages: A and B. If you submit a form on page > > A and navigate to page B, the view that JSF currently has stored is > > page B. So, if you use the browser's 'back' button to navigate to > > page A, JSF will take one request to synchronize the page and the > > view. Then the second request will be normal. > > > > I don't think that switching to client side state saving will change > > this behavior. > > > > > > On Sat, 13 Nov 2004 14:31:06 -0700, Arinaya <[EMAIL PROTECTED]> > > wrote: > > > Hello All, > > > I hope someone can please help me with this -- > > > > > > Currently when I navigate back to a form that has previously been > > > submitted, using the browser back button, I need to click > > the submit > > > button twice in order for the form to actually resubmit. The first > > > click seems to reset the form, clearing any changes that have been > > > made to input fields since navigating back to the form. > > > > > > We are currently using server-side state saving method, and > > I thought > > > this might be the problem, so I tried switching this to client, > > > but then the FacesServlet throws a > > > java.io.NotSerializableException. > > > > > > Has anyone had either of these two problems? > > > How can I get the browser back button to work? > > > Using MyFaces 1.0.7. > > > > > > Thanks, > > > Arinaya > > > > > > > > > > > > -- > > If you don't have a GMail account, I probably have 5 invites. Just > > ask! -Heath Borders-Wing > > [EMAIL PROTECTED] > > > > -- If you don't have a GMail account, I probably have 5 invites. Just ask! -Heath Borders-Wing [EMAIL PROTECTED]
