Secure socket policy files for establishing secure socket connections

1. A method comprising:

establishing, by a computing system, a non-secure socket connection with a policy file server;

requesting, by the computing system, a socket policy file via the non-secure socket connection;

receiving, by the computing system, a placeholder socket policy file in response to said request via the non-secure socket connection, wherein the placeholder socket policy file specifies to request the socket policy file via a first secure socket connection;

in response to said receiving the placeholder socket policy file, establishing, by the computing system, the first secure socket connection with the policy file server;

requesting, by the computing system configured by media content, the socket policy file from the policy file server via the first secure socket connection, wherein the socket policy file specifies a security policy governing socket connections for accessing additional media content on a content server over a transport protocol layer, wherein the security policy identifies (i) domains from which secure socket connections are required to communicate with the content server and (ii) domains from which non-secure socket connections are permitted to communicate with the content server;

receiving, by the computing system, the socket policy file via the first secure socket connection;

identifying, by the computing system, that the security policy requires communication with the content server via a second secure socket connection; and

communicating, by the computing system, with the content server via the second secure socket connection to access the additional media content.

2. The method of claim 1 , wherein the socket policy file is requested based on receiving, by an application executed at the computing system, input representing a command to execute media content hosted on the content server.

3. The method of claim 1 , wherein the policy file server and the content server are comprised in a single server system.

4. The method of claim 1 , wherein the policy file server is comprised in a first server system, the content server is comprised in a second server system, and the first server system and the second server system are hosted on a common network domain.

5. The method of claim 1 , further comprising:

said establishing, by the computing system, the first secure socket connection using a port, wherein the port comprises a socket connection end point for communicating with a server;

terminating, by the computing system, the first secure socket connection upon receiving the socket policy file; and

establishing, by the computing system, the second secure socket connection using the port.

6. The method of claim 1 , further comprising:

said establishing, by the computing system, the first secure socket connection using a first port;

terminating, by the computing system, the first secure socket connection after receiving the socket policy file; and

establishing, by the computing system, the second secure socket connection using a second port.

7. The method of claim 1 , wherein the socket policy file is an Extensible Markup Language (XML) file.

8. A computing system comprising:

a processor for executing instructions stored in a computer-readable medium on one or more devices providing an application;

wherein the application comprises one or more modules configured to perform operations when the computing system is configured by media content, the operations comprising:

establishing a non-secure socket connection with a policy file server;

requesting a socket policy file via the non-secure socket connection;

receiving a placeholder socket policy file in response to said request via the non-secure socket connection, wherein the placeholder socket policy file specifies to request the socket policy file via a first secure socket connection;

in response to said receiving the placeholder socket policy file, establishing the first secure socket connection with the policy file server;

requesting the socket policy file from the policy file server via the first secure socket connection, wherein the socket policy file specifies a security policy governing socket connections for accessing additional media content on a content server over a transport protocol layer, wherein the security policy identifies (i) domains from which secure socket connections are required to communicate with the content server and (ii) domains from which non-secure socket connections are permitted to communicate with the content server;

receiving the socket policy file via the first secure socket connection;

identifying that the security policy requires communication with the content server via a second secure socket connection; and

communicating with the content server via the second secure socket connection to access the additional media content.

9. The computing system of claim 8 , wherein the one or more modules are configured to perform additional operations comprising:

said establishing the first secure socket connection using a port, wherein the port comprises a socket connection end point for communicating with a server;

terminating the first secure socket connection upon receiving the socket policy file; and

establishing the second secure socket connection using the port.

10. The computing system of claim 8 , wherein the one or more modules are configured to perform additional operations comprising:

said establishing the first secure socket connection using a first port;

terminating the first secure socket connection upon receiving the socket policy file; and

establishing the second secure socket connection using a second port.

11. A computer-readable medium stored on a storage device, the computer-readable medium embodying program code executable by a computer system configured by media content, the computer-readable medium comprising:

program code for establishing a non-secure socket connection with a policy file server;

program code for requesting a socket policy file via the non-secure socket connection;

program code for receiving a placeholder socket policy file in response to said request via the non-secure socket connection, wherein the placeholder socket policy file specifies to request the socket policy file via a first secure socket connection;

program code for establishing, in response to said receiving the placeholder socket policy file, the first secure socket connection with the policy file server;

program code for requesting the socket policy file from the policy file server via the first secure socket connection, wherein the socket policy file specifies a security policy governing socket connections for accessing additional media content on a content server over a transport protocol layer, wherein the security policy identifies (i) domains from which secure socket connections are required to communicate with the content server and (ii) domains from which non-secure socket connections are permitted to communicate with the content server;

program code for receiving the socket policy file via the first secure socket connection;

program code for identifying that the security policy requires communication with the content server via a second secure socket connection; and

program code for communicating with the content server via the second secure socket connection to access the additional media content.

12. The computer-readable medium of claim 11 , further comprising:

program code for said establishing the first secure socket connection using a port, wherein the port comprises a socket connection end point for communicating with a server;

program code for terminating the first secure socket connection upon receiving the socket policy file; and

program code for establishing the second secure socket connection using the port.

13. The computer-readable medium of claim 11 , further comprising:

program code for said establishing the first secure socket connection using a first port;

program code for terminating the first secure socket connection upon receiving the socket policy file; and

program code for establishing the second secure socket connection using a second port.