LVE EP limit and HTTP2?

[noyearzero]

Just looking for some insight into how EP limits work with HTTP2. If I understand correctly, in HTTP1, browsers typically obeyed the 6-8 requests per domain at 1 time. So if 6 visitors visited a site at the same time, there would never be more than 48 simultaneous requests to the server. So an EP limit of 50 makes sense.

With HTTP2, I know it works a bit differently. A website request only opens up 1 "connection", but can request up to 100 resources at a time. So what is counted towards the EP limit? Is it the 1 connection, or does each resource count? If its each resource, and the EP limit is 50, then it seems like a web page with more than 50 resources on the same domain could be having EP faults quite often.

[apb]

It is actually connections to backend (PHP handler) that are counted against EP limit, so it doesnt matter how many TCP connections are used for that.

[noyearzero]

Interesting, thanks for the clarification. The docs talk about "apache slots" which is very misleading then, right? Because static assets are still served through apache. It may also makes it confusing for those who dont use apache.

Out of curiosity, would it be theoretically possible (or should I say realistic) to create a DDoS attack by requesting large static assets from a server?

[apb]

> Out of curiosity, would it be theoretically possible (or should I say realistic) to create a DDoS attack by requesting large static assets from a server?

Yes, this is possible with apache web server and LVE cant help in such cases.

[noyearzero]

Thanks. One last question hopefully:

Suppose I set the EP limit extremely high, but kept all other LVE at default settings. Would this pose any risk to the server, or would the other LVE limits kick in and protect the server from being taken down by 1 account?

[apb]

Other limits will still be active and will effectively limit resources consumed by any customer they are applied to.

[noyearzero]

I understand that. I guess what Im asking is: do EP limits protect against a situation that the other limits cant protect against? In particular, a situation that could cause an issue for the whole server.

[apb]

Ryan,

NPROC is the closest equivalent, but it might not be helpful here as well... Weve seen similar behavior (high EP count) with HTTP/2 and websites serving images from MySQL DB via PHP. If this is the case, you may need to set up MySQL Governor limits instead - do not hesitate to reach out to our support if you are not sure how to choose the right values.