pagure: disable /blame/ on pagure.io

The blame endpoint gets crawled a lot by scrapers and it's very
intensive for pagure. It has to run the blame in the git repo, which
can take a while and requests pile up.

While right now load is fine with it, it's might be causing
sporadic 503's that we are seeing cloing things. If there's a bunch
of blame requests cloging up the queue.

Users can git clone and run a blame locally if they need to.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>

roles/pagure/templates/0_pagure.conf

@@ -181,6 +181,11 @@ MaxConnectionsPerChild 1000
   #  RewriteEngine On
   #  RewriteCond %{REQUEST_URI} ^/linux-forgeperf.*$
   #  RewriteRule .* - [F]
+  # reject /blame endpoints for now.
+  # They cause pagure to take a while to process and pile up requests.
+  # Users can just git clone and run blame there if they need to.
+  RewriteCond %{REQUEST_URI} ^/.*/blame/.*$
+  RewriteRule .* - [F]
 
 # Spiders-gone-wild
 # These spiders may not follow robots.txt and will