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 resource. This method > exists primarily to allow the output of a POST-activated script to > redirect the user agent to a selected resource. The new URI is not a > substitute reference for the originally requested resource. The 303 > response MUST NOT be cached, but the response to the second > (redirected) request might be cacheable. > > The different URI SHOULD be given by the Location field in the > response. Unless the request method was HEAD, the entity of the > response SHOULD contain a short hypertext note with a hyperlink to the > new URI(s). > > Note: Many pre-HTTP/1.1 user agents do not understand the 303 > status. When interoperability with such clients is a concern, > the > 302 status code may be used instead, since most user agents > react > to a 302 response as described here for 303. > > As tested in my browser, we need 303 status, instead of 302. But > don't see wrapper like HttpResponseRedirect to do this. So I am > curious, I am the only one that want to use status 303? > > Thanks.
Setting the status to whatever you want is fairly straightforward. If you find yourself in need to use it frequently, you can define a subclass of HttpResponse, that sets the necessary information as needed. You can file a ticket with the code attached, if you believe it should be included in the framework. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
