"max connections"

[rejetto]

I wonder if the option "max connections" is really any good or if it only makes problems.
I saw several cases of people having problems, because the browser doesn't behave well with the way HFS is refusing the connection.
I made several attempts at changing the method (backlog, not accepting, aborting), and several research, but nothing improved.
I think I should remove this option.

[NaitLee]

How about a "max connections before limiting speed" or "max connections before stop offering file(main/html) page"?

[rejetto]

sorry but i don't understand what you mean by that/those

[NaitLee]

Just some suggestions if "max connections" is getting removed. They are useful for lowering server payload, but not too hard as refusing connections.

[rejetto]

ok but i'm not seeing how  your suggestion is going to NOT have the same problems. Can you explain?

[NaitLee]

Most of the "max connections limit" disadvantages are page half-loaded, such as the icon-hidden problem happened just now, or external css/js missing problem.
If we just limit speed after reaching a connection limit, similar confusing problems will be less; or we just stop offering HTML pages, as this can explain the limit situation clearly to page viewers.

[danny]

To avoid 'right click save as corrupt file' a redirect is needed; however, can't redirect from [overload] when already past the limit; therefore, must use disconnect to defeat the masquerade. 
Solution:   

Code: [Select]

[overload]
{.if|{.{.calc|{.get ini|max-connections.}.}<>0.}|{:{.set ini|max-connections=-1.}:}.}{.disconnect.}{.add to log|%ip% %user% disconnected at %connections% connections.}Global max connections limit = ddos so that is unset; and then, the remaining possibility is per-ip connections limit which is repurposed as a miscreant disconnector+logger.