[SOLVED] POSTDATA expired message on back button. Apache 1.3

Need help installing PHP, configuring a script, or configuring a server? Then come on in and post your questions! We'll try to help the best we can!

Moderator: General Moderators

Post Reply
zwxetlp
Forum Newbie
Posts: 3
Joined: Fri Apr 15, 2005 12:44 pm

[SOLVED] POSTDATA expired message on back button. Apache 1.3

Post by zwxetlp »

Im having some issues with a server. When a page is received using post, and you move on to another page, pressing the back button produces a warining that states that the "POSTDATA expired from cache" message and requires the user to press continue. Another server (both Apache 1.3) does not produce this message. The code on both servers is identical. Initially I though it was a client issue, but with the same browser visiting both sites one site will produce the message and another will not. Is this a setting in the apache conf?

Any help appreciated.
User avatar
feyd
Neighborhood Spidermoddy
Posts: 31559
Joined: Mon Mar 29, 2004 3:24 pm
Location: Bothell, Washington, USA

Post by feyd »

this typically has to do with the headers sent in the page requests.

Compare the headers sent from both servers. If you don't find the problem, this topic has been talked about here on many occasions.
zwxetlp
Forum Newbie
Posts: 3
Joined: Fri Apr 15, 2005 12:44 pm

Re: POSTDATA expired message on back button. Apache 1.3

Post by zwxetlp »

zwxetlp wrote:Im having some issues with a server. When a page is received using post, and you move on to another page, pressing the back button produces a warining that states that the "POSTDATA expired from cache" message and requires the user to press continue. Another server (both Apache 1.3) does not produce this message. The code on both servers is identical. Initially I though it was a client issue, but with the same browser visiting both sites one site will produce the message and another will not. Is this a setting in the apache conf?

Any help appreciated.
Solved.

For those interested, it turns out it was not a setting in the apache conf but rather a setting ("session_cache_limiter") in the php.ini file.

Thanks.
Post Reply