Include port when creating a pattern for a HTTPS URL

chrome/browser/content_settings/host_content_settings_map.cc

Index: chrome/browser/content_settings/host_content_settings_map.cc
diff --git a/chrome/browser/content_settings/host_content_settings_map.cc b/chrome/browser/content_settings/host_content_settings_map.cc
index 419921c23aea505d460f80ff72188db5a3e8bf06..827682819ff57c1c386b99a6e7e80c677946ce87 100644
--- a/chrome/browser/content_settings/host_content_settings_map.cc
+++ b/chrome/browser/content_settings/host_content_settings_map.cc
@@ -366,6 +366,9 @@ void HostContentSettingsMap::AddExceptionForURL(
 
   // Make sure there is no entry that would override the pattern we are about
   // to insert for exactly this URL.
+
+  // TODO(markusheintz): For cookies, the pattern and wildcard parameter need
+  // to be switched.

[Bernhard Bauer, 2011/06/22 09:49:11]

It should be correct this way; we switched to primary and secondary URLs and
patterns instead of top-level/embedded exactly to get that right (as in: the
primary URL for cookies is the cookie URL, while for most other types it's the
top-level frame URL, and we add wildcards for the secondary URL).

[markusheintz_, 2011/06/22 10:53:08]

+1 for Bernhard's comment.

That's way easier to maintain as the host content settings map should not need
to care about the semantics of the primary and secondary pattern.

   SetContentSetting(ContentSettingsPattern::FromURLNoWildcard(primary_url),
                     ContentSettingsPattern::Wildcard(),
                     content_type,