Sybille Peters wrote in #note-6:
About the DOS attacks or too many requests - should that not be better handled elsewhere, preferably before the attacker reaches TYPO3 / PHP or even the webserver?
I agree that it does not make much sense to implement a DOS protection in PHP, that should prevent overloading PHP resources.
Such protections (if necessary) should indeed be applied in a different layer of the network stack.
There are however scenarios, where rate limiting should be applied on functionality that is related to the application domain.
Examples for these are:
- authentication requests for a specific user account (currently implemented)
- contact form submissions
- etc.
These use cases (and all I had in mind) were related to incoming requests.
Sybille Peters wrote in #note-5:
I assume you are looking at incoming requests. I would also like to add outgoing requests - the mechanisms (API) used might be similar.
e.g. throttle outgoing HTTP requests in linkvalidator (and elsewhere?).
But the currently introduced Symfony rate limiting API is very generic. Without looking at the concrete implementation of this API,
I would assume it could be used to limit this interaction as well. Not sure though. I'd create a new ticket for each concrete use case anyway and within that ticket, we can evaluate options about possible implementations.
In any case, this ticket here is resolved from my pov with the given implementation. I will therefore close it.