[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sqwebmail
Subject:    [sqwebmail] Re: Corrupted messages list screen
From:       Sam Varshavchik <mrsam () courier-mta ! com>
Date:       2004-03-19 23:32:00
Message-ID: cone.1079739120.13950.14278.501 () ny ! email-scan ! com
[Download RAW message or body]


Ex Arca writes:

> When the user hits the BACK button within the framework of sqwebmail:
> 
> 1) Does the browser look only in a local cache for the previous page?  Thus 
> Apache and sqwebmail could not be responsible for the curruption.
> 
> 2) Or does sqwebmail still get invoked in someway. For example, maybe 
> sqwebmail does a re-authentication when going back to the message list?

That depends on the browser.

SqWebMail explicitly sends headers that direct the browser and any 
intermediate web caches not to cache any content for any reason.

A properly-behaving browser should try to re-fetch the older URL.

What actually happens in your case is something that only you can figure 
out.


[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]