i have an issue where a container security monitoring solution puts itself in the middle as a docker socket, but replies with HTTP 1.1.