Re: FastCGI env-vars

2017-07-05 Thread Jacob Champion
On 07/02/2017 08:44 AM, William A Rowe Jr wrote: I'm reading https://tools.ietf.org/html/rfc3875#section-4.1.5 as the PATH_INFO is entirely distinct from QUERY_STRING. Right. SCRIPT_NAME, PATH_INFO, and QUERY_STRING are intended to be three distinct parts of the Script-URI (see Section 3.3).

Re: FastCGI env-vars

2017-07-02 Thread William A Rowe Jr
I'm reading https://tools.ietf.org/html/rfc3875#section-4.1.5 as the PATH_INFO is entirely distinct from QUERY_STRING. On Sun, Jul 2, 2017 at 10:08 AM, Jim Jagielski wrote: > There is one (I hope!) final question... There seems to be > conflicting interpretations on whether

Re: FastCGI env-vars

2017-07-02 Thread Jim Jagielski
There is one (I hope!) final question... There seems to be conflicting interpretations on whether PATH_INFO should, or should NOT, include any QUERY_STRING info or "extra stuff" after the actual path itself... Right now, we don't.

Re: FastCGI env-vars

2017-06-30 Thread Jacob Champion
On 06/30/2017 09:43 AM, Jim Jagielski wrote: In any case, I think HEAD of the perl test framework is finally in shape to test and catch expectations regarding how we handle FCGI env-vars, both in "generic" situations as well as how php-fpm sees/expects them. At least, the current rev "passes"

FastCGI env-vars

2017-06-30 Thread Jim Jagielski
In any case, I think HEAD of the perl test framework is finally in shape to test and catch expectations regarding how we handle FCGI env-vars, both in "generic" situations as well as how php-fpm sees/expects them. At least, the current rev "passes" all tests based on my assumptions on what those