5 ms·
Browsers usually limit the number of requests to a certain domain (around 8 requests if I'm not mistaken, but it may vary). So I don't think it'd be the cause o
by Colex 9y ago
Browsers usually limit the number of requests to a certain domain (around 8 requests if I'm not mistaken, but it may vary). So I don't think it'd be the cause of a self inflicted DOS.
Also, every solution must be used carefully where it makes sense, if it doesn't make sense, then a different solutions must be thought of.
- ewalk153 9y agoIt takes the total cost to a server to render a page and multiplies it. Under low load, it could make it faster for one user. Under higher load, each initial page request will be more expensive and therefore will result in exhausted resources sooner.
- mnarayan01 9y agoTrue, though note that the limit is on active requests on the browser end (obviously). If your subrequests are "heavy" and the user refreshes a bunch, you're now going to have 6x (or 8x or whatever the limit is on their browser) the number of "zombie" requests still being processed on your server.
- nateberkopec 9y agoOnly over an HTTP/1 connection. Chrome and FF limit it to 6.
- mtarnovan 9y agoThat's incorrect. Browsers limit request to 8 req/domain at the same time.
- mtarnovan 9y agoDon't know why I was downvoted. For reference: https://en.wikipedia.org/wiki/HTTP_persistent_connection#Use_in_web_browsers https://en.wikipedia.org/wiki/HTTP_persistent_connection#Use... The limit applies only to persistent connections.