[BUG] Salt API 3004.2 returning empty response when calling GET minions endpoint /minions/<mid>

Description
After some amount of calls to the SALT API checking if a minion exists I get empty responses from minions that do exist. When I call the SALT api I get empty response (16 bytes) and status code 200, but when I call salt 'minion1' test.ping from the command line, I get the proper response True. The amount of calls is 60 in parallel every 5 seconds.

[27/Jun/2023:03:54:45] "GET /minions/minion1 HTTP/1.1" 200 16 "" "Go-http-client/1.1"

Setup

Custom options that might be relevant:

worker_threads: 12
sock_pool_size: 15

System setup:

• VM running in Linode: 6 CPU Cores, 16 GB RAM
• used bootstrap to install

Steps to Reproduce the behavior
We are calling the salt api multiple times in parallel. 60 calls in parallel every 5 seconds.

Expected behavior
If the salt-api is overloaded why is it not returning 429 or 500 status code, it's returning 200 instead.

Start with the Salt API GET /minions/ endpoint and the configured worker_threads and sock_pool_size values. Reproduce the reported 60-parallel-calls-every-5-seconds workload, compare the API response with salt 'minion1' test.ping, and inspect whether overloaded requests return an empty 200 response. Done means the behavior is understood and the endpoint returns a meaningful response or appropriate error status under load.