Unable to reload application into a browser after logging ou

For questions and postings not covered by the other forums
ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

Unable to reload application into a browser after logging ou

Postby ConvertFromOldNGs » Fri Aug 07, 2009 12:20 pm

by kirsty >> Mon, 20 Jan 2003 13:34:00 GMT

We have reimplemented the removeSessionWithMessage method on currentSession to present a simple message to the user when logging out of the client.

This works fine, however when we attempt to log back into the client after logging out, we get a WebSessionTimedOut page. This is the message we are currently supplying on the invalidWebSession method.

Can someone tell me why it is that subsequent login attempts cause this to happen, and how we might get around the problem.

ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

Re: Unable to reload application into a browser after logging ou

Postby ConvertFromOldNGs » Fri Aug 07, 2009 12:20 pm

by skipton >> Tue, 28 Jan 2003 0:11:02 GMT

Hi Kirsty,

Browsers do have a habit of caching web pages even when sometimes you dont want it too. Maybe whats happening is your browser has cached the previous session and is attempting to send this again. Since you have logged out Jade will not recognise the session id when you pass back in a cached page. You could check this is the problem by noting the id (located inside the html in your original session), then seeing what it is in the browser just prior to failing.

If this is the problem, then I hope you (or someone else) can come up with a better solution to the following .

Do a google search on "html no-cache" and read up on this.

What Im not sure of is how you get these META tags into the <HEAD> section of the HTML given Jade looks after this part. Try
1) playing round with the WebHTML control, you might be able to achieve it with this.
2) reimplementing the WebSession method (I think its "reply()" you want) so you can manipulate the HTML prior to it going out to the browser.

You may have to delete all your temporary browser files before any of this will work aswell.

Hopefully there is a neater solution than this that someone can provide, but atleast this might help you to work out what the problem is! If there isn't, then I would suggest forwarding the problem onto JadeSupport as this maybe a useful addition to the generated HTML.

Cheers,

John Beaufoy
JBS Solutions Ltd (UK)
john@jbssolutions.co.uk


Return to “General Discussion”

Who is online

Users browsing this forum: Bing [Bot] and 23 guests

cron