podman failure due to strong regex filter (pull request attached)

[container@144 ~]$ CONTAINER_HOST=tcp://localhost:2375 podman container ls
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: ping response was 403

[container@144 ~]$ podman container logs -f dockerproxy2 
[WARNING] 320/134849 (1) : Can't open server state file '/var/lib/haproxy/server-state': No such file or directory
Proxy dockerbackend started.
Proxy dockerfrontend started.
[NOTICE] 320/134849 (1) : New worker #1 (2) forked
10.0.2.100:40466 [17/Nov/2023:13:48:58.158] dockerfrontend dockerfrontend/<NOSRV> 0/-1/-1/-1/0 403 189 - - PR-- 1/1/0/0/0 0/0 "GET /v4.6.1/libpod/_ping HTTP/1.1"

Cause: regex filter is too strong for podman.
Remedy: Pull request #113 adds an optional url level matching the libpod keyword (or any other keyword)

Review pull request #113 first, since the issue identifies it as the proposed remedy for the strong regex filter. Confirm that URL-level matching can optionally recognize the libpod keyword or another keyword, and use the Podman request shown in the issue as the completion case.