You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the endpoint /delay/XXX, we experience that is does not work as documented when the delay is 30 seconds or longer.
I start podinfo like this:
The following test shows that it is not a timeout before I reach the container, as a request for /delay/40 takes 40 seconds, as it should. It just does not give a reply.
% time curl http://localhost:9898/delay/40
curl: (52) Empty reply from server
curl http://localhost:9898/delay/40 0.00s user 0.01s system 0% cpu 40.028 total
anderius
changed the title
Empty reply from server on delays >= 30s
Empty reply from server on delays ≥ 30s
Mar 5, 2025
When using the endpoint
/delay/XXX
, we experience that is does not work as documented when the delay is 30 seconds or longer.I start podinfo like this:
A delay below 30 seconds works as expected:
A delay of 30 seconds (or above) gives no response
I want to use podinfo for testing timeouts in the infrastructure, but this behavior makes that difficult.
The text was updated successfully, but these errors were encountered: