https://bz.apache.org/bugzilla/show_bug.cgi?id=70030

--- Comment #8 from Philippe Cloutier <[email protected]> ---
(In reply to Rich Bowen from comment #7)
> Cookies *are* headers, but I suppose I don't object to that too much. But
> that wasn't intended to be a comprehensive list, so I'm not sure that we
> need to add stuff. I suppose that could go either way.
Cookies are transmitted using headers, but they *are* not headers. That being
said, the reason I added it there was to avoid the redundancy in the current
version (although as I wrote, I suspect “server variables” remains redundant
with “environment variables”).

> But relegating pathinfo to only CGI is confusing, and nobody uses CGI any
> more, so they'll think "that doesn't apply to me," when it in fact might.
The change does not intend to "relegate" PATH_INFO to only CGI”, the
parenthesis only indicates it *corresponds*. It's far from perfect, but without
any precision, it's very likely that readers will:
1. think PATH_INFO is a variable just like QUERY_STRING
2. confuse PATH_INFO with PHP pathinfo()
3. or just not understand what PATH_INFO means.

If the parenthesis is deemed more confusing than the above and nobody
volunteers a better version, I would recommend to just drop that mention,
possibly linking to an authoritative definition, since a URL path always
includes PATH_INFO anyway.

> Augmenting the mention of query string by saying query string again also
> doesn't appear to accomplish anything.
The point was to keep the focus on a functional description, and de-emphasize
implementation details (variable names). But replacing the parenthesis with a
link to the section which describes %{QUERY_STRING} could look less redundant.

> The last part of the diff is just changing line wrapping, right?
Oh, I saw that pitiful line and thought my changes had made it lonely, so I
joined it with its neighbor. Sorry, I realize that wrapping was pre-existing
and that is indeed the only change I made there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to