Add rate limiting on /browse/content/ and browse/content/<>/raw
It seems a crawler start to use this endpoint to massively download content files.
Is-it possible to add the support for a rate limiting configuration for these endpoints?
It seems a crawler start to use this endpoint to massively download content files.
Is-it possible to add the support for a rate limiting configuration for these endpoints?
changed the description
I am considering using django-ratelimit package to add rate limit to views used to get contents.
mentioned in merge request !1265 (merged)
closed