Posted by petersprc on 10/30/07 14:39

There are no clients in widespread use that behave the way you
describe. This is an http issue, not html.

On Oct 30, 8:32 am, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> petersprc wrote:
> > On Oct 29, 6:24 am, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> >> petersprc wrote:
>
> >> > Try using session_cache_limiter('nocache') before session_start. This
> >> > will tell the browser not to cache the page.
>
> >> > Regards,
> >> > John Peters
>
> >> (Top posting fixed)
>
> >> Which the browser can ignore, unfortunately. And even if the browser
> >> doesn't ignore the cache, any of the systems between the client and the
> >> server could cache it.
>
> >> How I wish it did work properly.
>
> >> P.S. Please don't top post.
>
> > This combination of headers will be honored by most hosts/proxies. In
> > a situation where it's not, you can try using URL-based sessions or
> > putting your site under https.
> >
>
> (Top posting fixed - again).
>
> Not necessarily. Some do, some don't. And in some cases it depends on
> the browser settings. The same is true with https:.
>
> But this should be discussed in alt.html - this is not a PHP problem.
>
> And again - please don't top post. This group uses bottom posting or
> interwoven posting.
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstuck...@attglobal.net
> ==================

[Back to original message]