On Jan 27, 2008 5:55 AM, Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote:
> > For them, the best approach is to return 201 Created instead of a > redirect – the URI of the new resource still goes in the Location > header with 201. Then you render the item into the request body > and set Content-Location equal to Location. That's a strong > assertion that the body is the same representation that the > client would GET from the URI in the Location header, so > sufficiently savvy clients won't bother requesting it. > Are FF & IE smart enough to not re-POST if I send the results with A 201 instead of redirecting to a GET? Len [EMAIL PROTECTED] 614-404-4214
_______________________________________________ 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/
