4 ms·
HTTP allows a TimedOut response to be sent by a server to request you haven't yet sent. So it's not strictly request/reply.
by secondcoming 5y ago
HTTP allows a TimedOut response to be sent by a server to request you haven't yet sent. So it's not strictly request/reply.
- saba2008 5y ago'100 Continue' would probably be better example of breaking request/reply flow, as it provides useful functionality and requires non-trivial implementation and compatibility measures. While '408 Request Timeout' is somewhat dubious fig leaf over TCP RST