in reply to Re: Re^2: Falling for the same trap - since 1942
in thread Falling for the same trap since 1942

What's the problem he is trying to solve with redirects?

Refreshing. If you POST to a URL, then get back a page, and then try to refresh that page, you have to resend the POST data. If on the other hand, any URL you POST to produces a redirect, then refreshing will reload from the URL the refresh pointed you to, rather than the one you POSTed to.

It is in this context that following the GET/POST convention is most natural; of course, you can apply the general "redirect after everything that changes server state" even if you don't. Personally, I don't consider the "POSTs must have side effects" rule nearly as strong as the "GETs must never change server state" counterpart.

LISP: pure, clean, fun.
Don't forget "slow" and "memory hungry", esp in the case of LISP-ish Perl. And though I was referring to these connotations as well, I don't see what's so bad about being pragmatic? :-)

Makeshifts last the longest.

  • Comment on Re^4: Falling for the same trap - since 1942