CGI module redirect defaults to 302 -- why?
- From: Mott.Jeff@xxxxxxxxx
- Date: 29 Apr 2007 09:37:53 -0700
If the 302 status code is received in response to a request
other than GET or HEAD, the
user agent MUST NOT automatically redirect the request unless
it can be confirmed by the
user.
-- HTTP/1.1
For a CGI program that was requested from a POST form, the 302 message
seems to not be what I would want. But 303:
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.
HTTP/1.1
303 seems to be designed *exactly* for redirecting the browser after a
CGI program has run. Why then does the CGI module return a 302
response by default?
.
- Follow-Ups:
- Re: CGI module redirect defaults to 302 -- why?
- From: Mumia W.
- Re: CGI module redirect defaults to 302 -- why?
- Prev by Date: Re: a problem about function returning point
- Next by Date: Re: Top Turds of comp.lang.perl.misc (2007)
- Previous by thread: a problem about function returning point
- Next by thread: Re: CGI module redirect defaults to 302 -- why?
- Index(es):
Relevant Pages
|