Unfork IDS_PAGE_INFO_NON_SECURE_TRANSPORT into IDS_PAGEINFO_NOT_SECURE_SUMMARY

ios/chrome/browser/ui/dialogs/nsurl_protection_space_util.mm

Index: ios/chrome/browser/ui/dialogs/nsurl_protection_space_util.mm
diff --git a/ios/chrome/browser/ui/dialogs/nsurl_protection_space_util.mm b/ios/chrome/browser/ui/dialogs/nsurl_protection_space_util.mm
index 0ffb4d3ce4acb533e7db91bacf9f8fc462584836..b4bee1dae7e0bcb7e35922ab5ab3ae44424a72ac 100644
--- a/ios/chrome/browser/ui/dialogs/nsurl_protection_space_util.mm
+++ b/ios/chrome/browser/ui/dialogs/nsurl_protection_space_util.mm
@@ -26,7 +26,7 @@ NSString* MessageForHTTPAuth(NSURLProtectionSpace* protectionSpace) {
     return RequesterIdentity(protectionSpace);
 
   NSString* securityWarning =
-      l10n_util::GetNSString(IDS_PAGE_INFO_NON_SECURE_TRANSPORT);
+      l10n_util::GetNSString(IDS_PAGEINFO_NOT_SECURE_SUMMARY);

[estark, 2017/04/28 04:49:31]

It's a little weird that these http auth dialogs use PAGEINFO strings, isn't it?
Do they have anything to do with page info or does the string just happen to be
appropriate?

[meacer, 2017/04/28 15:28:40]

ISTR they were added when we decided we couldn't reliably display SSL info on
the HTTP auth dialog. I wonder why it always says "not secure" though, that
doesn't sound right. It could be for proxy auth dialogs, I'll need to check.

   return
       [NSString stringWithFormat:@"%@ %@", RequesterIdentity(protectionSpace),
                                  securityWarning];