https://bz.apache.org/bugzilla/show_bug.cgi?id=70035
Bug ID: 70035
Summary: RewriteOptions Directive: AllowAnyURI specification
calls Request-URI “request URI”
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: All
URL: https://httpd.apache.org/docs/trunk/en/mod/mod_rewrite
.html#rewriteoptions
OS: All
Status: NEW
Severity: trivial
Priority: P3
Component: Documentation
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
The RewriteOptions Directive specification starts its definition of AllowAnyURI
as follows:
> When RewriteRule is used in VirtualHost or server context with version 2.2.22
> or later of httpd, mod_rewrite will only process the rewrite rules if the
> request URI is a URL-path.
This is confusing, as no URI is a URL-path. In that sentence, "request URI"
actually means “Request-URI”, a confusing HTTP 1 term which has been replaced
with “request target” in HTTP 2.
That being said, I strongly suspect that would still be wrong today, as a
request target is not necessarily relative these days.
I am guessing the following would reflect reality:
> When rewrite rules are used in VirtualHost or server context, mod_rewrite
> will only process them if the request target is a valid URI reference.
> To lift the restriction, the AllowAnyURI option can be enabled, and
> mod_rewrite will apply the rule set to any request target, regardless of
> whether that string matches the grammar required by the HTTP specification.
🅭🄍: https://www.philippecloutier.com/Common+infrastructure+licensing#its
--
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]
