URL Signature #12
-
Thanks for this fantastic repo @shinsenter. You're bypassing URL signatures by default and it's not possible with the current NGINX rules to add them back. Would you mind commenting on
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @mdmm13 Thank you for your interest and for posing your question. I'll address your inquiries individually based on my knowledge.
In terms of mitigating DoS attacks, one effective strategy is to implement rewrite rules to restrict access to specific parameters that are necessary. For instance, in my current setup, I only allow resizing for images with fixed widths of 200, 640, 800, 1200, and 1600 pixels. Any other sizes default to 200 pixels. Lines 132 to 142 in 0d0bbe8 Additionally, implementing proxy caching between nginx and imgproxy can also significantly reduce the number of requests reaching imgproxy. docker-imgproxy/nginx/nginx.conf Lines 207 to 209 in 0d0bbe8 And if you use a CDN, this DoS limitation will be even more effective.
The main objective of my project is to minimize the number of parameters and URL signatures required for image query URLs. If you're interested in incorporating URL signatures into your setup, you can refer to how I utilize rewrite rules to achieve a similar outcome for adding URL signatures to imgproxy queries. Best regard |
Beta Was this translation helpful? Give feedback.
Hi @mdmm13
Thank you for your interest and for posing your question. I'll address your inquiries individually based on my knowledge.
In terms of mitigating DoS attacks, one effective strategy is to implement rewrite rules to restrict access to specific parameters that are necessary. For instance, in my current setup, I only allow resizing for images with fixed widths of 200, 640, 800, 1200, and 1600 pixels. Any other sizes default to 200 pixels.
docker-imgproxy/imgproxy.conf
Lines 132 to 142 in 0d0bbe8