Re: why there is no something like HttpResponseRedirect but status is 303

I read the source code a little. I know it is very easy. Because it is too easy (but still not done till now), and I think 303 status should be very common, I suspect that maybe I misunderstand something, or may 303 status is not so suitable in common cases. As the standard says: Many pre-HTT

Re: why there is no something like HttpResponseRedirect but status is 303

On 18/04/07, Gilbert Fine <[EMAIL PROTECTED]> wrote: > > Hi All, > >According to HTTP standard, the meaning of 303 status is (copied > from rfc2616): > > 10.3.4 303 See Other > > The response to the request can be found under a different URI and > SHOULD be retrieved using a GET method on that