4 ms·
Summary: HTTP pipelining isn't relevant any longer because we're all on broadband. Because the server has to send out the responses in the order that the orig
by kiwidrew 18y ago
Summary: HTTP pipelining isn't relevant any longer because we're all on broadband. Because the server has to send out the responses in the order that the original requests were received, the server may need to buffer a response if it is ready before the previous responses have been sent. Thus a malicious client could request a page which takes a long time to generate (e.g. a complex database query) followed by 99 other requests (as there is a limit of 100 requests in a single pipeline) and force the server to buffer the final 99 responses until the first request has completed.
Basically, the author rants about pipelining being useless
(even though it's quite useful in practice, particularly when serving static content from a separate domain) and then tries to claim that a minor denial-of-service attack is a huge security risk and that this is justification for not using pipelining.
- cperciva 18y agoforce the server to buffer the final 99 responses until the first request has completed. Except that most or all servers won't generate the final 99 responses until the first request has completed... in fact, most or all servers won't even read the final 99 requests until the first request has completed.