NYCPHP Meetup

[Chris Shiflett]

--- "Nunez, Eddy" <enunez at tiaa-cref.org> wrote:
> > The most common approach is to use an intermediate page for
> > processing, so that the POST request does not exist in the browser's
> > history mechanism.
> 
> Does this mean that the intermediate page processes and generates an
> output file (or something) to redirect the user to?

The intermediate "page" generates no output and has:

header('Location: http://newurl/');

> It makes sense to me, but would there be a better way than generating
> a temporary results page?

Yes, I think the better solution is to find the Cache-Control directives
that are best for your situation. In most every case, you can eliminate
whatever behavior you dislike this way. However, using an intermediate
page is more common, because it is easier to implement, and it is more
reliable (it doesn't rely as much on browser interpretation).

Hope that helps.

Chris

=====
Chris Shiflett - http://shiflett.org/

PHP Security Handbook
     Coming mid-2004
HTTP Developer's Handbook
     http://httphandbook.org/