[Bug 70096] New: URL-path misleading (excludes PATH_INFO)
[email protected] Fri, 29 May 2026 13:11:37 +0000
| Newsgroups | gmane.comp.apache.documentation |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bz.apache.org/bugzilla/show_bug.cgi?id=3D70096
Bug ID: 70096
Summary: URL-path misleading (excludes PATH_INFO)
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: All
URL: https://httpd.apache.org/docs/trunk/en/mod/directive-d
ict.html#Syntax
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: P4
Component: Documentation
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
The DPI|discardpath section of the RewriteRule Flags page implies that
PATH_INFO is excluded from the URL-path:
> In per-directory context, the URL-path each RewriteRule compares against =
is the concatenation of the current URL-path and PATH_INFO.
Yet the Syntax section of the Terms Used to Describe Directives page simply
defines a URL-path as follows:
> The part of a URL which follows the scheme, hostname, and optional port, =
but precedes any query string =E2=80=94 for example, /path/to/file.html. Th=
e URL-path represents a web-view of a resource, as opposed to a file-system=
view.
One would imagine that the URL-path matches the URL path, but that is not
necessarily the case as the latter includes PATH_INFO. Having a misleading =
name
is one thing, but as a minimum prevention from confusion, the definition of
=E2=80=9CURL-path=E2=80=9D should leave no room for ambiguity. An example =
with a PATH_INFO
would help.
=F0=9F=85=AD=F0=9F=84=8D: https://www.philippecloutier.com/Common+infrastru=
cture+licensing#its
--=20
You are receiving this mail because:
You are the assignee for the bug.=