Fix to respect --explicitly-allowed-ports command line option-Chromium Side

content/public/common/content_switches.h

Index: content/public/common/content_switches.h
diff --git a/content/public/common/content_switches.h b/content/public/common/content_switches.h
index 903c76da6982109265e0da743152c5b34ac8ce57..6a95953497a72daea09e69ae73f5cd0f82287b3b 100644
--- a/content/public/common/content_switches.h
+++ b/content/public/common/content_switches.h
@@ -145,6 +145,7 @@ CONTENT_EXPORT extern const char kEnableVtune[];
 CONTENT_EXPORT extern const char kEnableWebGLDraftExtensions[];
 CONTENT_EXPORT extern const char kEnableWebGLImageChromium[];
 CONTENT_EXPORT extern const char kEnableZeroCopy[];
+CONTENT_EXPORT extern const char kExplicitlyAllowedPorts[];

[eroman, 2015/04/10 01:32:17]

The same flag shouldn't be defined in both content/ and chrome/.
Right now it looks like this is relying on the linker to find the definition in
chrome which is not good.

Remove the switch from chrome in favor of this one in content (and it needs to
be defined in content_switches.cc probably)

[Paritosh Kumar, 2015/04/10 12:34:32]

Thanks. Removing it. 
But, https://codereview.chromium.org/1036823003/#msg5 ???

[tyoshino (SeeGerritForStatus), 2015/04/13 14:28:16]

I just wanted to confirm what eroman@ had suggested. I'm fine with defining it
only in content_switches.h.

 CONTENT_EXPORT extern const char kExtraPluginDir[];
 CONTENT_EXPORT extern const char kForceDisplayList2dCanvas[];
 CONTENT_EXPORT extern const char kForceFieldTrials[];