Bug 63385 - hcuri is ignored when used with OPTIONS hcmethod
Summary: hcuri is ignored when used with OPTIONS hcmethod
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_hcheck (show other bugs)
Version: 2.4.39
Hardware: PC other
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: PatchAvailable
Depends on:
Reported: 2019-04-24 19:05 UTC by chrisjfuller
Modified: 2019-06-14 06:45 UTC (History)
0 users

Patch (1.38 KB, patch)
2019-06-14 06:44 UTC, Christophe JAILLET
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description chrisjfuller 2019-04-24 19:05:15 UTC
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

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

[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
[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.
Comment 1 Christophe JAILLET 2019-06-14 06:44:50 UTC
Created attachment 36626 [details]

Hi, could you try the attached patch?

Its purpose is to behave the same with OPTIONS, HEAD or GET when an hcuri is configured, and fallback to "*" for OPTIONS if hcuri is not provided.