DELIVERING AUTO-PLAY MEDIA CONTENT ELEMENT FROM CROSS ORIGIN RESOURCES

• US 20180253415A1
• Filed: 03/01/2017
• Published: 09/06/2018
• Est. Priority Date: 03/01/2017
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Halai, Murtaza, Thompson, Lloyd Dee, Mulford, Brian, Mkrtchyan, Armen
• Granted Patent: US 10,733,376 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: G06F 40/221 Parsing markup language streams streaming G06F40/149
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Systems and methods for delivering cross-site auto-play media are described herein. The server can receive, from a client device, a request for media content at a first domain embedded in a content element from a second domain. The request can include an identifier indicating that the client device is configured to restrict cross-domain redirection. The server can determine, responsive to identifying the identifier indicating that the client device is configured to restrict cross-domain redirection, that the request comprises a content type header having a first predetermined value. The server can generate, responsive to the determination, a response comprising the media content element in a body of the response. The server can transmit the response to the client device. Receipt of the response can cause the client device to extract the media content element from the body of the response and to render the media content element.

Claims

1. A method for delivering cross-site auto-play media, comprising:

receiving, by a data processing system from a client device, a request for media content at a first domain embedded in a content element from a second domain, the request including a predefined identifier indicating that the client device is configured to restrict cross-domain redirection;

determining, by the data processing system, responsive to identifying the first domain as different from the second domain and to identifying the predefined identifier indicating that the client device is configured to restrict cross-domain redirection, that the request comprises a content type header having a first predetermined value;

generating, by the data processing system, responsive to determining that the request comprises the content type header having the first predetermined value, a response comprising the media content element in a body of the response; and

transmitting, by the data processing system, the response to the client device, receipt of the response causing the client device to render the media content element in the body of the response.

2. The method of claim 1, wherein receiving the request for media content element further comprises receiving the request for media content element, the request including a device type identifier for the client device;

and

wherein the method further comprises;

determining, by the data processing system, that the client device is configured to restrict automatic rendering of the media content element encoded in a first format based on the device type identifier, and

transcoding, by the data processing system, responsive to determining that the client device is the mobile device, the media content element from the first format to a second format, the client device configured to restrict automatic rendering of the media content element encoded in the first format and to permit rendering the media content element encoded in the second format.

3. The method of claim 1, wherein receiving the request for media content element further comprises receiving the request for media content element, the predefined identifier of the request including an application type identifier for an application executing on the client device;

and

wherein the method further comprises;

identifying, by the data processing system, that the application type identifier for the application executing on the client device corresponds to a predesignated application, and

determining that the request comprises the content type header having the first predetermined value, responsive to identifying that the application type identifier corresponds to the predesignated application.

4. The method of claim 1, further comprising searching, by the data processing system, a whitelist for the first domain, the whitelist specifying a plurality of domains permitted with the embedded media content element;

and

wherein generating the response further comprises generating the response responsive to determining that the first domain is on the whitelist.

5. The method of claim 1, further comprising:

receiving, by the data processing system from a second client device, a second request for media content element at a third domain embedded in a content element from a fourth domain, the second request including the predefined identifier indicating that the second client device is configured to restrict cross-domain restriction;

determining, by the data processing system, responsive to identifying the third domain as different from the fourth domain and to identifying that the second request includes the predefined identifier, that the second request comprises a content type header having a second predetermined value different from the first predetermined value;

generating, by the data processing system, responsive to determining that the request comprises the content type header having the second predetermined value, a second response comprising an address for requested media content element in a body of the second response and a status identifier indicating success in a header of the second response; and

transmitting, by the data processing system, the second response to the second client device, receipt of the second response causing the second client device to transmit a third request for the requested media content element to the extracted address.

6. The method of claim 5, further comprising determining, by the data processing system, responsive to receiving the second request from the second client device, that a number of redirect requests for the second client device is less than a predefined threshold;

and

wherein determining that the second request comprises the content type header type having the second predetermined value further comprises determining that the second request comprises the content type header type having the second predetermined value, responsive to determining that the number of redirect requests is less than the predefined threshold.

7. The method of claim 5, wherein the second predetermined value of the content type header in the second response indicates textual content.

8. The method of claim 1, wherein the first predetermined value of the content type header in the response indicate non-textual content.

9. The method of claim 1, wherein generating the response further comprises generating the request including executable code in the body of the response to instantiate a media player.

10. The method of claim 1, wherein the response comprises a status code lacking a redirect code.

11. A system for delivering cross-site auto-play media, comprising:

a response parser executed on a data processing system with one or more processors, configured to;

receive a request for media content at a first domain embedded in a content element from a second domain, the request including a predefined identifier indicating that the client device is configured to restrict cross-domain redirection, and

determine, responsive to identification of the first domain as different from the second domain and to identification of the predefined identifier indicating that the client device is configured to restrict cross-domain redirection, that the request comprises a content type header having a first predetermined value; and

a response rewriter executed on the data processing system, configured to;

generate, responsive to determination that the request comprises the content type header having the first predetermined value, a response comprising the media content element in a body of the response, and

transmit the response to the client device, receipt of the response configured to cause the client device to render the media content element from the body of the response.

12. The system of claim 11, wherein the request includes a device type identifier for the client device;

wherein the request handler is further configured to determine that the client device is configured to restrict automatic rendering of the media content element encoded in a first format based on the device type identifier; and

wherein the system further comprises a media encoder configured to, responsive to the determination that the client device is the mobile device, the media content element from the first format to a second format, the client device configured to restrict automatic rendering of the media content element encoded in the first format and to permit rendering the media content element encoded in the second format.

13. The system of claim 11, wherein the predefined identifier of the request includes an application type identifier for an application executing on the client device;

and

wherein the request handler is further configured to;

identify that the application type identifier for the application executing on the client device corresponds to a predesignated application, and

determine that the request comprises the content type header having the first predetermined value, responsive to the identification that the application type identifier corresponds to the predesignated application.

14. The system of claim 11, wherein the request handler is further configured to search whitelist for the first domain, the whitelist specifying a plurality of domains permitted with the embedded media content element;

and

wherein the response rewriter is further configured to generate the response responsive to determining that the first domain is on the whitelist.

15. The system of claim 11, wherein the request handler is further configured to:

receive a second request for media content element at a third domain embedded in a content element from a fourth domain, the second request including the predefined identifier indicating that the second client device is configured to restrict cross-domain restriction, and

determine, responsive to identification of the third domain as different from the fourth domain and to identifying that the second request includes the predefined identifier, that the second request comprises a content type header having a second predetermined value different from the first predetermined value; and

wherein the response rewriter is further configured to;

generate, responsive to the determination that the request comprises the content type header having the second predetermined value, a second response comprising an address for requested media content element in a body of the second response and a status identifier indicating success in a header of the second response, and

transmit the second response to the second client device, receipt of the second response causing the second client device to transmit a third request for the requested media content element to the extracted address identified in the body of the response.

16. The system of claim 15, wherein the request handler is further configured to:

determine, responsive to the receipt of the second request from the second client device, that a number of redirect requests for the second client device is less than a predefined threshold; and

determine that the second request comprises the content type header type having the second predetermined value, responsive to determining that the number of redirect requests is less than the predefined threshold.

17. The system of claim 15, wherein the second predetermined value of the content type header in the second response indicates textual content.

18. The system of claim 11, wherein the first predetermined value of the content type header in the response indicate non-textual content.

19. The system of claim 11, wherein the response rewriter is further configured to generate the request including executable code in the body of the response to instantiate a media player.

20. The system of claim 11, wherein the response comprises a status code lacking a redirect code.