Switch web API/permission code to use IsOriginSecure() instead of SchemeIsSecure().

content/browser/appcache/appcache_update_job.cc

Index: content/browser/appcache/appcache_update_job.cc
diff --git a/content/browser/appcache/appcache_update_job.cc b/content/browser/appcache/appcache_update_job.cc
index 4b212861222e0f15a560f871888c4f64860f7ed2..708b42c32a2996f93fc988ec50bccec5c13d9b80 100644
--- a/content/browser/appcache/appcache_update_job.cc
+++ b/content/browser/appcache/appcache_update_job.cc
@@ -169,7 +169,7 @@ void AppCacheUpdateJob::URLFetcher::OnResponseStarted(
     return;
   }
 
-  if (url_.SchemeIsSecure()) {
+  if (url_.SchemeIsCryptographic()) {

[lgarron, 2015/04/27 23:21:53]

michaeln@: I think the following code requires the connection to be, well...
cryptographic.
In case you're not up to speed on the changes, we're replacing SchemeIsSecure()
with SchemeIsCryptographic() or with OriginIsSecure(), depending on what's
appropriate.

Is SchemeIsCryptographic() correct here, or would something else be more
accurate?

[palmer, 2015/04/30 19:05:11]

I think in general we want to deprecate AppCache in favor of Service Workers,
and |SchemeIsCryptographic| keeps the scope of AC strictly narrower than does
|IsOriginSecure|. So let's use |SchemeIsCryptographic| unless michaeln has a
great reason otherwise.

Note also that |SchemeIsCryptographic| is a much closer analogue to
|SchemeIsSecure| than |IsOriginSecure| is.

     // Do not cache content with cert errors.
     // Also, we willfully violate the HTML5 spec at this point in order
     // to support the appcaching of cross-origin HTTPS resources.