https://bz.apache.org/bugzilla/show_bug.cgi?id=63385
Bug ID: 63385
Summary: hcuri is ignored when used with OPTIONS hcmethod
Product: Apache httpd-2
Version: 2.4.39
Hardware: PC
OS: other
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_hcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
When configuring mod_proxy_hcheck to use hcmethod=options, the hcuri is
ignored.
Configuration example:
<Proxy balancer://test>
BalancerMember https://www.example.com/ hcmethod=OPTIONS hcuri=/path/test
</Proxy>
Access log on health check target:
[24/Apr/2019:18:33:12 +0000] "OPTIONS * HTTP/1.0" 200 126 "-" "-"
Meanwhile, changing the hcmethod to either GET or HEAD shows the hcuri
parameter is respected. For example:
<Proxy balancer://test>
BalancerMember https://www.example.com/ hcmethod=GET hcuri=/path/test
</Proxy>
[24/Apr/2019:18:35:33 +0000] "GET ///path/test HTTP/1.0" 404 466 "-" "-"
<Proxy balancer://test>
BalancerMember https://www.example.com/ hcmethod=HEAD hcuri=/path/test
</Proxy>
[24/Apr/2019:18:36:17 +0000] "HEAD ///path/test HTTP/1.0" 404 159 "-" "-"
rfc2616 states that the OPTIONS method can be used to determine the capability
of a specific resource but that a * can be used simply as a ping, so this may
be by design.
"If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to
apply to the server in general rather than to a specific resource. Since a
server's communication options typically depend on the resource, the "*"
request is only useful as a "ping" or "no-op" type of method; it does nothing
beyond allowing the client to test the capabilities of the server."
However, it would be useful to mirror the functionality of the GET and HEAD
hcmethods and have the OPTIONS hcmethod respect the hcuri.
--
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]
