Oh, one more thing.
what I'm really trying to avoid is the user using the "back" button, so
I've added the following to my pages
<% response.setHeader("Pragma","no-cache");%>
<% response.setHeader("Cache-Control","no-store");%>
<% response.setDateHeader("Expires",-1);%>
Now, when I use the back button, I get the expided page... page. When I
reload, I get the error 500
Should I take a step back here and simply be handling things like that in a
different way? I want the user to use the "back button" I've provided since
it cleans appropriate things up, etc... not the back browser button.
thoughts?
On 5/26/05, David Johnson <[EMAIL PROTECTED]> wrote:
>
> Thanks Wendy! I'll take a look at it... and likely still be confused :)
>
> On 5/26/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> >
> > From: "David Johnson" <[EMAIL PROTECTED]>
> > > Can you tell me a little more about how you're setting this up then?
> > Should
> > > I then just create an error.jsp page that is outside my tiles setup,
> > and
> > > handle the error there?
> >
> > Can you keep it from getting as far as an error code 500? You can
> > configure
> > exception handlers in struts-config.xml using the <exception> tag.
> >
> > For me, the mapping in web.xml for error code 500 is a last ditch effort
> > to
> > avoid the user seeing a stack trace. It should only come into play if
> > something REALLY bad happens.
> >
> > See if anything here is helpful...
> > http://wiki.wendysmoak.com/cgi-bin/wiki.pl?TomcatErrorPage
> > and the related page
> > http://wiki.wendysmoak.com/cgi-bin/wiki.pl?StrutsException
> >
> > --
> > Wendy Smoak
> >
> >
>
>
> --
> -Dave
> [EMAIL PROTECTED]
--
-Dave
[EMAIL PROTECTED]
