There's no "cache://" "protocol". This is simply Google's search query parser being extremely forgiving with "cache://" vs "cache:", which is the correct syntax (as documented on various sites on the internet).
When you type "cache:" or "cache://" into Chrome (FF not tested) you'll see the top result it's about to execute is a search. It just sends the string to google.com.
If you go to google.com manually and input "cache:www.example.com" as the search query, you won't get a results page, you'll go directly to the cached page.
There's no "cache://" "protocol". This is simply Google's search query parser being extremely forgiving with "cache://" vs "cache:", which is the correct syntax (as documented on various sites on the internet).
When you type "cache:" or "cache://" into Chrome (FF not tested) you'll see the top result it's about to execute is a search. It just sends the string to google.com.
If you go to google.com manually and input "cache:www.example.com" as the search query, you won't get a results page, you'll go directly to the cached page.