<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
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.<br>
<br>
--S<br>
<br>
<div class="moz-signature"><span style="color: rgb(102, 0, 0);">Stuart
Watt<br>
ARM Product Developer<br>
Information Balance</span></div>
<br>
On 6/2/2010 1:56 PM, <a class="moz-txt-link-abbreviated" href="mailto:will@serensoft.com">will@serensoft.com</a> wrote:
<blockquote
cite="mid:AANLkTim2D-np8rMqD1UgI_aLP6xZWIiO1UEsoUx9Sizs@mail.gmail.com"
type="cite">
<div>Short version:</div>
<div>
<div><br>
</div>
<div>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?</div>
<br>
</div>
<pre wrap="">_______________________________________________
List: <a class="moz-txt-link-abbreviated" href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a>
Listinfo: <a class="moz-txt-link-freetext" href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a>
Searchable archive: <a class="moz-txt-link-freetext" href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a>
Dev site: <a class="moz-txt-link-freetext" href="http://dev.catalyst.perl.org/">http://dev.catalyst.perl.org/</a>
</pre>
</blockquote>
</body>
</html>