Hi Admin,
I think there are different cases and different scenarios there and thus should be handled differently.
My inquiry didn’t assume that the website is full of bugs or has security issues in the first place (because I won’t get that simply from the term “overloaded”, maybe it’s mentioned in the tickets idk, at least not in this post). I agree that insecure websites or websites that endanger others should be suspended with a chance for the web admin to rectify for sure. No hosting would allow insecure websites on their infrastructure afaik across the industry.
Burst of traffic, if legitimate, should be entertained, but since free hosting has a daily limit then I don’t think this would be an issue for discussion, limit is limit, it’s a numbers talk. As for infinite loops, we have max_execution_time in place so that should in theory be taken care of as well.
Memory leaks and other factors are the answers to my initial inquiry, given that the source code caused those leaks like didn’t close connections or MySQL queries.
No, simple as that. Why should others bear the burden? I don’t see how that’s related to my inquiry tho tbh.
I’m not sure how this free hosting is set up and I have no idea or initiative to go too deep in this aspect, but I do expect a stable performance on a normal secure website that runs within the set limits. How one website can affect another on the same machine completely depends on the server infrastructure which I believe is a business secret and I won’t dive deep on that subject. Subsequent follow-up money-talk questions therefore skipped, I’m only interested in the technical possibility part and the reason part.
Maybe the suspension message should say something like “insecurity factors found on the current website that causes overload” so web admins can understand what they have done wrong and not be confused.
Understandably it’s not feasible to have staff look through codes to say something like “this part has something that goes wrong”, but some hints/directions can help a long way. Even as simple as “abnormal high traffic detected, please implement security measures, etc.” would be much more helpful than “overload the servers”, especially when the target audience is mostly newbies that are trying out the hosting technology.
In case web admins do want to figure it out, then this community is definately the place for them to seek help.
I agree, this is something that the programmer should consider if their feature could be abused in certain ways, or is their current setup strong enough to withstand the expected high traffic.
As logs are not available on free hosting, it would be quite difficult for web admins to know their website is receiving high traffic. A notification after is not something that they could respond to when the thing is in action, but at least they know something happened, and they have to implement a fix the day after (if they have the chance to).
Cheers!