[FX.php List] Page expired problem

[Troy Meyers]

It seems I've seen a thread about this already, but I don't recall a satisfactory conclusion.

We've been running a web site using CDML and FMU 6 for a number of years. We recently switched to FMSA 8 and kept the CDML by using the new Blackbelt software, which reads the CDML and interprets it on the fly into PHP and works via FX.php

There is an issue that has cropped up, where some users are getting a "page expired" error when they click the back-button. This is happening in places where they are used to being able to use the back button. I don't think this can be entirely blamed on the resubmission of POST data, since the POST vs. GET methods haven't been changed in this implementation.

I did a little eavesdropping on the web page headers, and there is a difference between what FMU 6 used to send and Blackbelt/PHP/FMSA8.

Here's a typical header from FMU6:

HTTP/1.1 200 OK
Date: Mon, 07 May 2007 16:45:38 GMT
Server: FileMakerPro/6.0v4 WebCompanion/6.0v3
MIME-Version: 1.0
Transfer-Encoding: chunked
Content-Type: text/html

...and here's what one for the same page in Blackbelt/PHP/FMSA8 looks like:

HTTP/1.1 200 OK
Date: Mon, 07 May 2007 16:50:26 GMT
Server: Apache/1.3.33 (Darwin) PHP/5.1.2 mod_jk/1.2.3-dev
X-Powered-By: PHP/5.1.2
Set-Cookie: PHPSESSID=81b3uan78ha6fhd0qa686mfg50; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html

One of the new items in the header is Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, and also Pragma: no-cache ...and those might be making the difference. It's also interesting that the Expires: is stamped way in the past!

Any idea if these are the culprits, and if there is anything I can do about them?

-Troy