httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Behlendorf <br...@organic.com>
Subject Re: Patch to mod_cgi
Date Fri, 07 Jun 1996 04:01:41 GMT
On Thu, 6 Jun 1996, Chuck Murcko wrote:
> > There's a way around this - make the CGI (or the server itself using
> > Redirect) issue a redirect to the new location. 
> > 
> No, it gets weirder, Brian. And Brian Clapper will no doubt correct me if I'm
> wrong. 8^)
> 
> We thought of doing a redirect (in fact, bmc tested that).
> 
> It turned his POST data into GET data. 8^(
> 
> This is a real bizarre set of constraints he has to work within.

Aarg - okay, I went to the source, the HTTP/1.0 spec, and looked at the 
descriptions of 301 and 302, and saw a

  Note: When automatically redirecting a POST request after receiving a 301
        status code, some existing user agents will erroneously change it 
        into a GET request.

Hmmm, if a CGI outputs a Location: header, doesn't the redirection happen 
internally?

Ugh.  

Okay, another solution: use mod_negotiation, and have script.cgi actually 
be script.cgi.ncgi (where .ncgi is the nph-) and give nph- some really 
high q value.  It's a stretch, but it might work....

nph- POST-handling scripts - whoa.

	Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com  |  We're hiring!  http://www.organic.com/Home/Info/Jobs/


Mime
View raw message