Hi Nuno,

I�m sure it�s not a simple timeout problem. It happens even when I use my
aplication for just 10 seconds.
I have already checked to see if there is some forced session closing but I
could not find one.

But, I have observed this behaviour just in Cach� 4.1.13 and 4.1.16, when I
use 4.0.3 it runs without this expiration problem.
In 4.0.3 I could use the browser�s BACK without expiration problems.

Thanks, Carlos.

"Nuno Canas" <[EMAIL PROTECTED]> escreveu na mensagem
news:[EMAIL PROTECTED]
> Hi Carlos,
> If I could understand you in English - I'm shure I will in Portuguese -
> your problem is just a "Session TimeOut".
> I'm not a big expert on Cache like Peter, Kevin, Sukesh, Bill, etc...
> So (In my pages I've made a CSR - Rule that checks for %session
> variables and if they not exist it does a redirect to the Login Page.
>
> I suspect it's because your session is timming out and the page
> (CSPToken) variable is expired.
>
> Somenone correct me if I'm wrong.
>
> this is the code I use to check if the user exists:
>
> <csr:RULE name="IsUser" match="IsUser" empty>
> <csr:ACTION>
> <script language="cache" runat="server">
> if $l($G(%session.Data("UserId")))=0 {
> w "<script language='javascript'>",!
> w "self.document.location='../Login.csp'",!
> w "<"_"/script>"
> }
> </script>
> </csr:ACTION>
> </csr:RULE>
>
>
> Nuno
>
>
> Carlos Castro wrote:
>
> > Hi All,
> >
> > I have a CSP application that uses private pages for security reasons
and it
> > is runing well but, when I use the "back" from browser it returns me, in
> > some pages (not in all the pages), a warning that the page was expired.
What
> > could be the reason?
> >
> > I�m using cach� 4.1.13 (Build 212U).
> >
> > Thanks, Carlos.
> >
> >
>



Reply via email to