Re: mod_cgi/7580: [PATCH] CGI environment REQUEST_URI did not hold original URI after redirection

[rb...@apache.org]

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: [PATCH] CGI environment REQUEST_URI did not hold original URI after redirection

State-Changed-From-To: open-closed
State-Changed-By: rbb
State-Changed-When: Mon Sep  3 18:38:02 PDT 2001
State-Changed-Why:
I have backed out this change.  It is very important that
we be compatible with older versions of Apache, so that
migrating from Apache 1.3 to 2.0 is seamless for CGI
scripts.

Re: mod_cgi/7580: [PATCH] CGI environment REQUEST_URI did not hold original URI after redirection

[Ryan Bloom <rb...@covalent.net>]

On Monday 03 September 2001 20:45, William A. Rowe, Jr. wrote:

Bill, this is really simple.  In Apache 1.3, if I requested a CGI script, index.cgi
with

http://localhost/

the environment variable REQUEST_URI was set to 

/

Before this change, the environment variable REQUEST_URI was set to

/index.cgi

If this breaks anything in the server at all, then the whole server should be thrown
out, because it has horrible horrible problems.  We are just talking about reverting
back to the 1.3 behavior here.

Ryan

> I believe Microsoft solved this same quandry with another variable, which I
> can't put my fingers on at the moment.
>
> We also set QUERY_STRING_UNESCAPED, corresponding to the raw QUERY_STRING.
> Perhaps we offer the same for REQUEST_URI_UNESCAPED?
>
> Reading the PR subject, though, the key words were _after_redirection_.  It
> will NOT hold the original URI.  That would be REDIRECT_URL.
>
> Is this what you ment in your PR?
>
> Bill
>
> > State-Changed-From-To: open-closed
> > State-Changed-By: rbb
> > State-Changed-When: Mon Sep  3 18:38:02 PDT 2001
> > State-Changed-Why:
> > I have backed out this change.  It is very important that
> > we be compatible with older versions of Apache, so that
> > migrating from Apache 1.3 to 2.0 is seamless for CGI
> > scripts.

-- 

______________________________________________________________
Ryan Bloom				rbb@apache.org
Covalent Technologies			rbb@covalent.net
--------------------------------------------------------------

Re: mod_cgi/7580: [PATCH] CGI environment REQUEST_URI did not hold original URI after redirection

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

I believe Microsoft solved this same quandry with another variable, which I can't
put my fingers on at the moment.

We also set QUERY_STRING_UNESCAPED, corresponding to the raw QUERY_STRING.
Perhaps we offer the same for REQUEST_URI_UNESCAPED?

Reading the PR subject, though, the key words were _after_redirection_.  It will
NOT hold the original URI.  That would be REDIRECT_URL.

Is this what you ment in your PR?

Bill

> State-Changed-From-To: open-closed
> State-Changed-By: rbb
> State-Changed-When: Mon Sep  3 18:38:02 PDT 2001
> State-Changed-Why:
> I have backed out this change.  It is very important that
> we be compatible with older versions of Apache, so that
> migrating from Apache 1.3 to 2.0 is seamless for CGI
> scripts.
> 
>