- From: Willy Tarreau <w@1wt.eu>
- Date: Tue, 15 Sep 2020 04:09:00 +0200
- To: Eric J Bowman <mellowmutt@zoho.com>
- Cc: Ietf Http Wg <ietf-http-wg@w3.org>
On Mon, Sep 14, 2020 at 05:03:48PM -0700, Eric J Bowman wrote: > How many webservers implement the URI wildcard, i.e. > > http://example.com/* > > I've only ever implemented for OPTIONS requests. Is this obsolete, are there > successful use-cases, or do folks just not bother with this? Unless I'm mistaken, I think the URI wildcard is in fact "http://example.com" (with no trailing slash) which is turned to "*" when sent as a path component with the OPTIONS method. At least H2 agents are required to use "*" in the path for empty paths components (RFC7540#8.1.2.3) so it's likely that most H2 agents implement it. FWIW I've seen it work fine for upgrades at least. Willy
Received on Tuesday, 15 September 2020 02:09:16 UTC