From 02d42fda6dd56c8c1cd4af8c9c848fcc5210a370 Mon Sep 17 00:00:00 2001
From: Ken Sheedlo
Date: Tue, 13 Aug 2013 16:14:34 -0700
Subject: chore(minerr): move $sce:insecurl file to sce directory

Closes #3568
---
 docs/content/error/insecurl.ngdoc     | 26 --------------------------
 docs/content/error/sce/insecurl.ngdoc | 26 ++++++++++++++++++++++++++
 2 files changed, 26 insertions(+), 26 deletions(-)
 delete mode 100644 docs/content/error/insecurl.ngdoc
 create mode 100644 docs/content/error/sce/insecurl.ngdoc

diff --git a/docs/content/error/insecurl.ngdoc b/docs/content/error/insecurl.ngdoc
deleted file mode 100644
index b5d3ce84..00000000
--- a/docs/content/error/insecurl.ngdoc
+++ /dev/null
@@ -1,26 +0,0 @@
-@ngdoc error
-@name $sce:insecurl
-@fullName Processing of a Resource from Untrusted Source Blocked
-@description
-
-AngularJS' {@link api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL.
-
-Typically, this would occur if you're attempting to load an Angular template from an untrusted source.
-It's also possible that a custom directive threw this error for a similar reason.
-
-Angular only loads templates from trusted URLs (by calling {@link api/ng.$sce#getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL).
-
-By default, only URLs that belong to the same origin are trusted. These are urls with the same domain and protocol as the application document.
-
-The {@link api/ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL.
-
-To load templates from other domains and/or protocols, either adjust the {@link
-api/ng.$sceDelegateProvider#resourceUrlWhitelist whitelist}/ {@link
-api/ng.$sceDelegateProvider#resourceUrlBlacklist blacklist} or wrap the URL with a call to {@link
-api/ng.$sce#trustAsResourceUrl $sce.trustAsResourceUrl}.
-
-**Note**: The browser's {@link
-https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_XMLHttpRequest Same Origin
-Policy} and {@link http://www.w3.org/TR/cors/ Cross-Origin Resource Sharing (CORS)} policy apply
-that may further restrict whether the template is successfully loaded.  (e.g.  neither cross-domain
-requests won't work on all browsers nor `file://` requests on some browsers)
diff --git a/docs/content/error/sce/insecurl.ngdoc b/docs/content/error/sce/insecurl.ngdoc
new file mode 100644
index 00000000..b5d3ce84
--- /dev/null
+++ b/docs/content/error/sce/insecurl.ngdoc
@@ -0,0 +1,26 @@
+@ngdoc error
+@name $sce:insecurl
+@fullName Processing of a Resource from Untrusted Source Blocked
+@description
+
+AngularJS' {@link api/ng.$sce#strictcontextualescaping Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL.
+
+Typically, this would occur if you're attempting to load an Angular template from an untrusted source.
+It's also possible that a custom directive threw this error for a similar reason.
+
+Angular only loads templates from trusted URLs (by calling {@link api/ng.$sce#getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL).
+
+By default, only URLs that belong to the same origin are trusted. These are urls with the same domain and protocol as the application document.
+
+The {@link api/ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL.
+
+To load templates from other domains and/or protocols, either adjust the {@link
+api/ng.$sceDelegateProvider#resourceUrlWhitelist whitelist}/ {@link
+api/ng.$sceDelegateProvider#resourceUrlBlacklist blacklist} or wrap the URL with a call to {@link
+api/ng.$sce#trustAsResourceUrl $sce.trustAsResourceUrl}.
+
+**Note**: The browser's {@link
+https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_XMLHttpRequest Same Origin
+Policy} and {@link http://www.w3.org/TR/cors/ Cross-Origin Resource Sharing (CORS)} policy apply
+that may further restrict whether the template is successfully loaded.  (e.g.  neither cross-domain
+requests won't work on all browsers nor `file://` requests on some browsers)
-- 
cgit v1.2.3