how can I avoid a page expired error?

[NotGiven]

The user searches and see the results, then clicks for more detail in a
result. He then clicks the BACK button in the browser to see the results
again and....gets a page expired error.

How do you get around this?

[Sebastian Lauwers]

NotGiven wrote:

The user searches and see the results, then clicks for more detail in a
result. He then clicks the BACK button in the browser to see the results
again and....gets a page expired error.
I suppose the page expired thing is when iexplorer needs to resend post
data to the server? Not sure anymore, but you could try to open a
session, store the post data and do a header ("location:");.
How do you get around this?

HTH,
S.

--
The most likely way for the world to be destroyed,
most experts agree, is by accident.
That's where we come in; we're computer professionals.
We cause accidents.
--Nathaniel Borenstein

[steve]

"NotGiven" wrote:

The user searches and see the results, then clicks for more detail in a
result. He then clicks the BACK button in the browser to see the
results
again and....gets a page expired error.

How do you get around this?

I presume you are using a script from somewhere else. Check the html
source to set if there are any meta tags related to expiring (it is
easy to figure that out). If so, remove them from the php code.

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/PHP-avoid-pa...ict139664.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=467180

[Chung Leong]

"NotGiven" <no****@nonegiven.net> wrote in message
news:6U*****************@bignews4.bellsouth.net...

The user searches and see the results, then clicks for more detail in a
result. He then clicks the BACK button in the browser to see the results
again and....gets a page expired error.

How do you get around this?

Don't use POST for submitting the search.

[neur0maniak]

NotGiven wrote:

The user searches and see the results, then clicks for more detail in a
result. He then clicks the BACK button in the browser to see the results
again and....gets a page expired error.

How do you get around this?

I found that using "session_start()" on the page submitting the form, or
on the target using POST, then returning to the first page will give
this error. Instead, I was forced to use cookies instead of sessions.

[steve]

"neur0maniak" wrote:

NotGiven wrote:

The user searches and see the results, then clicks for more

detail in a

result. He then clicks the BACK button in the browser to see the results

again and....gets a page expired error.

How do you get around this?

I found that using "session_start()" on the page submitting the

form, or
on the target using POST, then returning to the first page will give this error. Instead, I was forced to use cookies instead of

sessions.

neur0maniak, I would not think so. After all, session and
cookie-based.

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/PHP-avoid-pa...ict139664.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=467729

[neur0maniak]

steve wrote:

"neur0maniak" wrote:

> NotGiven wrote:

> > The user searches and see the results, then clicks for more

detail

> in a

> > result. He then clicks the BACK button in the browser to see the

> results

> > again and....gets a page expired error.
> >
> > How do you get around this?
> >
> >

>
> I found that using "session_start()" on the page submitting the

form,

> or
> on the target using POST, then returning to the first page will

give

> this error. Instead, I was forced to use cookies instead of

sessions.

neur0maniak, I would not think so. After all, session and
cookie-based.

Try it and see for yourself.

Using a session_start() adds headers to the page that prevents caching
on the user's side

[R. Rajesh Jeba Anbiah]

steve <Us************@dbForumz.com> wrote in message news:<41**********@news.athenanews.com>...
<snip>

> I found that using "session_start()" on the page submitting the

form,

> or
> on the target using POST, then returning to the first page will

give

> this error. Instead, I was forced to use cookies instead of

sessions.

neur0maniak, I would not think so. After all, session and
cookie-based.

http://in.php.net/session_cache_limiter

--
| Just another PHP saint |
Email: rrjanbiah-at-Y!com

[name?]

"NotGiven" <no****@nonegiven.net> wrote in message news:<6U*****************@bignews4.bellsouth.net>. ..

The user searches and see the results, then clicks for more detail in a
result. He then clicks the BACK button in the browser to see the results
again and....gets a page expired error.

How do you get around this?

If you're using sessions, this is caused by the default value of
session.cache_limiter being 'no-cache' in your php.ini file. You'll
need to change it to a less-restrictive value, which may or may not be
a security issue. In your case (a search) I'd guess it's not, and a
value of 'private' would solve the problem. http://us4.php.net/session
has more detail on session.cache_limiter settings.