CiviCRM Community Forums (archive)

Sometimes when a Profile and its fields are made public and available to people, search engines can find it too.  Even when certain fields are made to be "Public User Pages" as opposed to "Public User Pages And Listings" it is still possible to search on fields that require a fair amount of database strength to execute these queries.  In the case of one of my clients, this was crashing the site.

For instance, even though our field "custom_12" is "Public User Pages" in our Profile, a URL such as this is not rejected by CiviCRM and it will still query the database.
http://www.example.com/civicrm/profile?force=1&gid=9&custom_12=Wetlands

I have devised a series of Rewrite Rules which could be placed in a Drupal .htaccess file

 RewriteCond %{QUERY_STRING} &?custom_
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]
  RewriteCond %{QUERY_STRING} &?city
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]
  RewriteCond %{QUERY_STRING} &?email
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]
  RewriteCond %{QUERY_STRING} &?postal_code
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]  
  RewriteCond %{QUERY_STRING} &?phone
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]
  RewriteCond %{QUERY_STRING} &?last_name
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]
  RewriteCond %{QUERY_STRING} &?first_name
  RewriteRule ^civicrm/profile http://www.example.org/foo.html? [R=302,L]  

These series of RewriteRules will send all inappropriate searches to a static HTML page, thereby saving a lot of RAM and CPU on your server.

These new rules should be placed before this line:

# Rewrite URLs of the form 'x' to the form 'index.php?q=x'.