We do a redirect code 303 from the POST request handler to a GET handler
and page through it instead. This appears to be the HTTP 1.1 norm, and
anything else is risky, as POST is expected to change stuff in the
database. Paging through a POST result will (might) cause multiple
changes. This way caching is supposed to be handled right.
--S
Stuart Watt
ARM Product Developer
Information Balance
On 6/2/2010 1:56 PM, w...@serensoft.com wrote:
Short version:
Using [% c.req.uri_with({ page => pager.next_page }) %] is fine for a
simple single-field search (where the form uses GET instead of
POST)... but how do we PAGE through (and/or cache) a multi-field form
search that uses POST?
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
