It's only blocked if you use https search, not if you use http. Most users don't use https and there doesn't seem to be any evidence that Google is going to re

It's only blocked if you use https search, not if you use http. Most users don't use https and there doesn't seem to be any evidence that Google is going to redirect http://www.google.com http://www.google.com to https, so they seem to be doing what you suggest already. On the https side, not passing the referrer is the correct behavior, and to do differently would break a great number of RFCs in all likelihood, as well as be unexpected/insecure behavior in an environment where the user has explicitly requested security. User preference trumps webmaster convenience, always.