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).
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
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.
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"
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