JP2009026010A - Content distribution device, content distribution control method, and content distribution control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To ensure a publication place for content such as an advertisement distributed by a content distribution network. <P>SOLUTION: The content distribution device is provided with a code provision means providing a code, which has functions for acquiring information of a server device as an acquisition source of page content and assigning content included in the page content, while adding a verification signature in response to access from a client terminal via a communication tag included in the page content acquired from another server device, a code verification means verifying whether a code activating access by the signature added in the access is authorized one or not in response to content assignment access by the code from the client terminal, a server verification means verifying whether content provision is allowed or not by information of the server device as the acquisition source of the page content added in the access, and a content provision means providing the content to be assigned to the client terminal. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a content distribution device, a content distribution control method, and a content distribution control program for distributing content such as advertisements on a network such as the Internet.

  Internet web pages contain content such as advertisements, and content data is acquired from the server (content distribution as viewed from the server) in the process of interpreting HTML (Hyper Text Markup Language) of the web page. Is called.

  FIG. 1 is a diagram showing an example of content distribution by a conventional Web server. A browser 11 of a client terminal 1 that browses a Web page of a Web server 3 refers to content on the same Web server 3. That is, the HTML of the Web page output from the Web server 3 and the content distributed from the Web server 3 are browsed by the same browser 11. Therefore, the display of content such as text and images can be controlled by the Web page, and it is possible to prevent only the content from being separated and displayed on another browser.

  On the other hand, when operating a Web system on the Internet, content distribution is separate from the Web server in order to achieve load distribution to the server, efficient distribution using a cache, and dynamic replacement of content included in a Web page. A server may be used. The content distribution server transmits content such as text and images (still images, moving images) from a content distribution server different from the Web server to which the user's browser refers, and displays the content on the browser. This mechanism is called a content delivery network (CDN).

As a content distribution method in the content distribution network,
(1) Content is distributed from the content distribution server by a distribution tag such as a “<img>” tag described in HTML page content (page data not including content received from the content distribution server) (2) Page content Distribution from the content distribution server by the described “<embed>” tag or the like (3) Generate a request to the content distribution server for content allocation of (1) and (2) above by JavaScript described in the page content is there.

  FIG. 2 is a diagram showing an example of content delivery by a conventional content delivery server, and FIG. 3 is a sequence diagram showing an example of the processing.

  2 and 3, content distribution is performed as follows.

  First, as a preparation, a delivery tag indicating the location of the content is embedded in a Web page on the Web server 3. FIG. 4A shows an example of a distribution tag. In the case of an image, “<img src =” http: // distribution server name /? contentid = 00001>, and in the case of Flash (Web content created by combining audio and vector graphics animation), “<embed src =“ http: // distribution server name /? contentid = 0001 ">", and in the case of text, "<script type =" javascript "src =" http: // distribution server name /? " contentid = 0001 ">".

  Next, returning to FIG. 3, when a Web page acquisition request is transmitted from the browser 11 to the Web server 3 (step S <b> 1), the Web server 3 includes a distribution tag on the Web server 3 in accordance with the request from the browser 11. The page (HTML) is returned to the browser 11 (step S2).

  Next, in the process of rendering the web page returned from the web server 3, the browser 11 transmits a content acquisition request to the content delivery server 4 described in the delivery tag (step S3).

  In accordance with the content acquisition request received from the browser 11, the content distribution server 4 acquires the content data from the content distribution server 4 or the content storage on the network (steps S4 and S5), and transmits the content data to the browser 11 (step S4). S6). FIG. 4B shows an example of content data to be transmitted, which is image data in the case of an image, Flash data in the case of Flash, and a JavaScript code for writing out text in the case of text.

  The applicant has not been able to find published prior art documents related to the present invention by the time of filing. Therefore, prior art document information is not disclosed.

  As described above, in order to operate a Web system on the Internet, a content distribution network that transmits content from a content distribution server that is different from the Web server that is referred to by the browser is desirable. In that case, there were the following problems.

  That is, in the case of a content distribution network in which the distribution route of HTML and content such as images is separated, whether the content distributed by the content distribution server is an HTML call output from a predetermined Web server (A), or other It is difficult to determine whether the call is based on HTML output from the Web server (B). For this reason, content held by the content distribution server can be freely referred to from the outside by copying a content distribution description (distribution tag) that is a content request to the content distribution server described in HTML to another Web page. It will end up.

  In particular, in the case of content related to advertisements, there are many contracts for content distribution specifying the domain, site, and URL where the advertisement is placed, and content such as banner ads and text ads are copied to external websites and web pages for distribution. It is not preferable to be done.

More specifically, the following points are problems.
(1) Mistake or falsification of distribution tag There is no means for suppressing distribution or detecting distribution abnormality in response to an act of mistakenly describing the distribution tag or deliberately rewriting the distribution tag. Therefore, there is a possibility that a situation in which content to be distributed to an appropriate place is not distributed.
(2) Movement of distribution tag (a) Since the distribution tag operates even if it is embedded in any web page, it is not a web page to which content is to be distributed or a web page on another web server. Will also be able to deliver content.

  (A) As a means for confirming the Web page in which the distribution tag is embedded, there is HTTP_REFERER that the browser sends to the content distribution server. However, REFFERER can be tampered with, and anti-virus software etc. Since there are cases where REFFERER transmission is restricted, this is not a reliable means.

  The present invention has been proposed in view of the above-described conventional problems, and an object of the present invention is to provide a content distribution apparatus and content capable of guaranteeing a place where content such as an advertisement distributed by a content distribution network is placed. A delivery control method and a content delivery control program are provided.

  In order to solve the above problems, in the present invention, as described in claim 1, access is accepted from a client terminal via a distribution tag included in page content acquired from another server device, and A device that distributes content to a client terminal, and acquires information of a server device from which the page content is acquired in response to access from the client terminal via the distribution tag, and content included in the page content A code providing means for providing a code having a function for assigning the content by adding a verification signature, and accessing with the signature added at the time of access according to the content assignment access by the code from the client terminal Verifies whether the code that triggered the is valid A code verification unit, and a server verification unit that verifies whether or not content provision is permitted by information of a server device that is an acquisition source of the page content added at the time of access when the code verification is normally performed; The gist of the present invention is a content distribution device that includes content providing means for providing content to be allocated to the client terminal when server verification is normally performed.

  Further, as described in claim 2, in the content distribution apparatus according to claim 1, the code verifying unit is configured to acquire a code acquired within a predetermined time from the current time by a time stamp added when the code is provided. It is possible to further perform time authentication as to whether or not the access is based on.

  Further, as described in claim 3, in the content distribution apparatus according to claim 1 or 2, the signature added by the code providing unit includes a content ID for uniquely identifying the content, A hash algorithm is applied to the combination of the domain of the server device that provides the page content, the time stamp indicating the time of processing, the user agent and IP address of the accessing client terminal, and the internal secret key. Can be generated.

  Further, as described in claim 4, in the content distribution device according to any one of claims 1 to 3, the access is added at the time of access from the client terminal via the distribution tag. A delivery tag verification means for verifying the validity of the delivery tag based on another signature included in the delivery tag can be provided.

  Further, as described in claim 5, in the content distribution device according to claim 4, the other signature includes a content ID that uniquely identifies the content, a domain of the server device that provides the page content, It can be generated by applying a hash algorithm to a combination of other secret keys inside.

  According to a sixth aspect of the present invention, there is provided a method of accepting access from a client terminal via a distribution tag included in page content acquired from another server device, and distributing the content to the client terminal, In response to access from the client terminal via the delivery tag, a code having a function of acquiring information of the server device from which the page content is acquired and assigning content included in the page content is used for verification. Whether the code activated by the signature added at the time of access is valid in accordance with the code providing step of providing with a signature and the content allocation access by the code from the client terminal Code verification process to verify A server verification process for verifying whether or not content provision is permitted based on information of the server device from which the page content is added, which is added at the time of access, and when the server verification is performed normally The content distribution control method can include a content providing step of providing the allocation target content to the client terminal.

  According to a seventh aspect of the present invention, there is provided a control program for a device that accepts access from a client terminal via a distribution tag included in page content acquired from another server device and distributes the content to the client terminal. The computer has a function of acquiring information of the server device from which the page content is acquired and assigning the content included in the page content in response to access from the client terminal via the distribution tag. A code providing means for providing a code with a verification signature, and a code that activates access by a signature added at the time of access according to content access by the code from the client terminal is valid Code that verifies whether or not When the verification means and the code verification are normally performed, the server verification means for verifying whether or not the content provision is permitted by the information of the server device that is the acquisition source of the page content added at the time of access is provided. It can be configured as a content distribution control program that functions as content providing means for providing the allocation target content to the client terminal when it is normally performed.

  In the content distribution apparatus, the content distribution control method, and the content distribution control program of the present invention, a code such as JavaScript is returned in response to access via a distribution tag included in the page content, and The content is provided according to the allocated access, and it is verified whether the code is valid or not by the signature added to the code, and the content is obtained from the information of the server device from which the page content acquired by the code is acquired. Since it is verified whether or not the provision is permitted, it is possible to guarantee the place where the content such as the advertisement distributed by the content distribution network is placed.

  Hereinafter, preferred embodiments of the present invention will be described.

<System configuration>
FIG. 5 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 5, a web server 3 and a content distribution server 4 are connected to a network 2 such as the Internet, and are connected to a client terminal 1 such as a PC (Personal Computer), a PDA (Personal Digital Assistants), or a mobile phone used by the user. The web server 3 and the content distribution server 4 can be accessed from the installed browser 11.

  The Web server 3 has a function of returning the page content P described in HTML stored in the storage 31 to the request source as a response in response to a request for acquiring page data based on HTTP (Hyper Text Transfer Protocol). The page content P includes an arbitrary number of distribution tags T for content acquisition. Although a specific example of the delivery tag T will be described later, the content of the JavaScript source having the function of acquiring the information of the Web server 3 from which the page content P is acquired and interpreting the content at the time of interpretation / execution at the client terminal 1 Used to obtain from the distribution server 4.

  The content distribution server 4 has an HTTP request receiving unit 41 that receives an HTTP request from the client terminal 1, and when the request is a JavaScript source acquisition request, the distribution tag T is valid according to a parameter added to the request. A distribution tag verification unit 42 that verifies whether or not the distribution tag T is valid, and a JavaScript generation unit 43 that generates a JavaScript source to be transmitted to the client terminal 1 when the distribution tag T is valid.

  In addition, when the request from the client terminal 1 is a content allocation request, the content distribution server 4 verifies whether the JavaScript is valid according to the parameter added to the request, and the JavaScript verifying unit 44 and the JavaScript. Whether or not content provision is permitted from the information (domain, URL) of the Web server 3 from which the page content P is acquired by the client terminal 1 according to the parameter added to the request. A URL verification unit 45 that verifies and a content acquisition unit 46 that acquires content from the content storage 40 inside the content distribution server 4 or on the network when content provision is permitted.

  In addition, the content distribution server 4 includes an HTTP response transmission unit 47 that transmits the JavaScript source generated by the JavaScript generation unit 43 or the content acquired by the content acquisition unit 46 to the client terminal 1 that is the request source.

  Furthermore, the secret key # 1 K1 used for the delivery tag verification in the delivery tag verification unit 42, the secret key # 2 K2 used for the JavaScript generation in the JavaScript generation unit 43 and the JavaScript verification unit 44 in the JavaScript generation unit 43, and the URL A URL table UT used for URL verification in the verification unit 45 is held.

<Operation>
FIG. 6 is a sequence diagram showing a processing example of the above embodiment.

  First, as a prior work, the delivery tag T is embedded in the page content P of the Web server 3. FIG. 7 is a diagram showing an example of a distribution tag T. As shown in FIG. 7A, as a parameter of a source acquisition destination URL (URL of the content distribution server 4), a content ID that uniquely identifies the content, and page content Including the domain of the Web server 3 that provides the signature and the signature # 1 for verifying the falsification of the information. The signature # 1 is generated by applying a hash algorithm such as HMAC-SHA1 to a combination of the content ID, the domain, and the secret key # 1.

  (B) shows a specific example of the distribution tag T embedded in the page content P, and the distribution tag T is embedded at a position where the content on the HTML should be displayed. “<Script ~> </ script>” indicates that a script such as JavaScript is described, “type =“ text / javascript ”” indicates that the type (type) is text or JavaScript, “Src =“ http: // content distribution server name / ”indicates the URL of the content distribution server 4. “ContentID = 0001” indicates a content ID, “domain = example.co.jp” indicates a domain, and “sig = Xp34iSXA” indicates a signature # 1.

  Returning to FIG. 6, when a web page acquisition request is made from the browser 11 of the client terminal 1 to the web server 3 (step S <b> 101), the web server 3 returns the web page HTML of the page content P including the delivery tag T to the browser 11. (Step S102).

  The browser 11 interprets the HTML of the received page content P and performs rendering (rendering), interprets the distribution tag T, and sends a JavaScript source acquisition request to the content distribution server 4 that is the source acquisition destination of the distribution tag T. Transmit (step S103). Note that the content ID, domain, and signature # 1 set in the distribution tag T are added as URL parameters to the JavaScript source acquisition request.

  When the content distribution server 4 receives the JavaScript source acquisition request by the HTTP request reception unit 41, the distribution tag verification unit 42 uses the signature # 1 included in the URL parameter to tamper with other parameters (content ID, domain). It is verified whether there is any (step S104). FIG. 8 is a diagram showing an example of delivery tag verification, which combines the content ID and domain of the URL parameter added to the JavaScript source acquisition request and the internal secret key # 1 (secret key # 1 K1 in FIG. 5). A signature for verification is generated by applying a hash algorithm such as HMAC-SHA1 to the object, and it is verified whether or not it matches the signature # 1 of the URL parameter added to the JavaScript source acquisition request. If the two match, it is determined that there is no falsification. If they do not match, record the fact in the log etc. as a possibility of falsification and use it for reference by the administrator.

Next, when the distribution tag is normally verified, the content distribution server 4 causes the JavaScript generation unit 43 to generate a JavaScript source return parameter and a JavaScript source (step S105).
FIG. 9A shows an example of a JavaScript script return time parameter. The content ID and domain of the URL parameter added to the JavaScript script acquisition request, the time stamp indicating the time of processing, and the signature # 2 are shown. Contains. The signature # 2 includes a content ID, a domain, a time stamp, a user agent (User-Agent: a character string indicating terminal information) and an IP (Internet Protocol) address acquired from the header of the HTTP request when receiving the JavaScript source acquisition request. And an internal secret key # 2 (secret key # 2 K2 in FIG. 5) are combined to generate a hash algorithm such as HMAC-MD5.

  FIG. 9B shows an example of a JavaScript source, a description D1 for setting a variable, a description D2 for content allocation in the case of text content, a description D3 for content allocation in the case of image content, Is included. Note that the description D3 is not included in the case of only text content, and the description D2 is not included in the case of only image content.

The meaning of each line of the description D1 is as follows.
・ "Var gdomain = document.domain;"
The domain value of the document object is assigned to the variable gdomain. That is, the domain value of the Web page referred to by the client terminal 1 at the time of executing JavaScript is set in the variable gdomain.
・ "Var url = document.URL;"
The url value of the document object is assigned to the variable url. That is, the url value of the Web page referred to by the client terminal 1 at the time of executing JavaScript is set in the variable url.
"Var ref = document.referrer;"
The referrer value of the document object is assigned to the variable ref. That is, the referrer value of the Web page that is referred to by the client terminal 1 when executing JavaScript is set in the variable ref.
・ "Var id = <content ID>;"
Set the content ID to the variable id. The content ID is the content ID of the parameter when the JavaScript script is returned.
・ "Var dm = <domain>;"
Set the domain in the variable dm. The domain is the domain of the JavaScript script source return parameter.
・ "Var ts = <timestamp>;"
A time stamp is set in the variable ts. The time stamp is a time stamp of a parameter when the JavaScript script is returned.
・ "Var ua = <user agent>"
Set the user agent in the variable ua. The user agent is a user agent used when generating a parameter when returning a JavaScript source.
"Var sig = <signature # 2>;"
Signature # 2 is set in variable sig. Signature # 2 is signature # 2 of the JavaScript script return parameter.
・ "Domain = URL_ENCODE (gdomain);"
Encode variable gdomain into a regular URL expression.
"Url = URL_ENCODE (url);"
Encode the variable url into a regular URL expression.
"Ref = URL_ENCODE (ref);"
Encode the variable ref into a regular URL expression.

  The description D2 is a part for writing out a tag for acquiring the text content. As parameters of the source acquisition destination URL (URL of the content distribution server 4), the content ID, domain, time stamp, signature # 2, acquisition domain, acquisition URL Includes referrer, get.

  The description D3 is a part for writing out a tag for acquiring the image content, and the content ID, domain, time stamp, signature # 2, acquisition domain, acquisition URL as parameters of the source acquisition destination URL (content distribution server 4 URL) Includes referrer, get.

  Returning to FIG. 6, the content distribution server 4 transmits the generated JavaScript source as a response to the browser 11 by the HTTP response transmission unit 47 (step S106).

  Next, the browser 11 executes the acquired JavaScript source (step S107). The domain, URL, and referrer of the page content P browsed by the browser 11 are acquired by executing the description D1 part of FIG. 9B, and the tag for acquiring the content is written by executing the description D2 or the description D3. . FIG. 10 is a diagram showing an example of data acquired by executing JavaScript in the browser 11, and shows that the domain, URL, and referrer are acquired by executing the part of the description D1 in FIG. 9B.

  Next, returning to FIG. 6, the browser 11 transmits a content allocation request to the content distribution server 4 that is the source acquisition destination in the process of interpreting the tag for content acquisition written by the execution of the JavaScript source (step S108). ). In this content allocation request, a content ID, a domain, a time stamp, a signature # 2, an acquisition domain, an acquisition URL, and an acquisition referer are added as URL parameters.

In the content distribution server 4, when the content allocation request is received by the HTTP request receiving unit 41, the JavaScript verification unit 44 verifies whether or not the JavaScript source is falsified by using the signature # 2 included in the URL parameter (step S109). ). In this JavaScript verification, the following two points are verified.
(A) Verification of whether the content ID, domain, and time stamp have been tampered with.
(A) Verification of whether or not access is performed by the same browser as the primary processing from the delivery tag verification (step S104) to the JavaScript script return (step S106).
(A-1) Verification of access by the same IP address and user agent as in the primary processing (guarantee of terminal identity).
(B-2) Verification of whether the elapsed time from JavaScript source return (step S106) to JavaScript verification (step S109) is within a predetermined time (1500 ms or the like) (preventing manual tampering).

  With these two items, the consistency of JavaScript is checked in the path from the JavaScript source return (step S106) to the content allocation request (step S108).

  FIG. 11 is a diagram showing an example of JavaScript verification. The content ID, domain, and time stamp of the URL parameter added to the content allocation request, and the user agent and IP address acquired from the HTTP request header when the content allocation request is received. And a secret algorithm # 2 (secret key # 2 K2 in FIG. 5) are combined with a hash algorithm such as HMAC-MD5 to generate a verification signature and added to the content allocation request It is verified whether or not it matches the signature # 2 of the URL parameter. Also, time verification is performed based on whether or not the time stamp of the parameter added to the content allocation request is greater than the current time minus a predetermined time (1500 ms in the figure). If both verifications are normal, it is determined that the JavaScript source has not been tampered with. If any of the verifications are negative, record that fact in the log for reference by the administrator.

  Next, returning to FIG. 6, if the content distribution server 4 determines that the JavaScript source has not been tampered with, the URL verification unit 45 converts the URL parameter acquisition domain, acquisition URL, and domain added to the content allocation request. Based on the URL table UT, URL verification is performed to determine whether or not content provision is permitted (whether or not the distribution tag is attached to the permitted distribution destination website) (step S110). FIG. 12 is a diagram showing an example of URL verification. As shown in (a), whether the acquired domain and the domain match, and whether the domain (acquired domain) and the acquired URL are registered in association with the URL table UT. Verify whether or not. (B) shows an example of the URL table UT, in which domains and permitted / non-permitted URLs are registered in advance in association with each other.

  Next, returning to FIG. 6, if the content distribution server 4 determines that content provision is permitted as a result of the URL verification, the content acquisition unit 46 performs content from the content storage server 4 inside the content distribution server 4 or on the network. Content data corresponding to the ID is acquired (steps S111 and S112).

  In the content distribution server 4, the HTTP response transmission unit 47 transmits the content data to the browser 11 (step S113). FIG. 13 is a diagram illustrating an example of content to be distributed. In the case of text content, a JavaScript source for writing the content content is included as in description D11, and in the case of image content, image data is included as in description D12. .

  Note that the primary processing (steps S104 to S106) and the secondary processing (steps S109 to S113) depend on the host of the content distribution server 4 to pass parameters between the browser 11 and the content distribution server 4 and perform validation. do not do. Therefore, it functions effectively even when the name of the content distribution server 4 is DNS round robin or when there are a plurality of servers under the load balancer.

<Summary>
As described above, the embodiment of the present invention has the following advantages.
(1) A place where a content such as an advertisement distributed by a content distribution network can be guaranteed, and the content can be protected.
(2) It is possible to prevent the act of wasting resources of the content distribution server by copying the distribution tag to other than the permitted domain.
(3) It is possible to effectively prevent mistakes and falsification of the delivery tag.
(4) The distribution destination can be controlled only by the browser without depending on the encryption method of the communication path or the introduction of the plug-in.
(5) Even when the names of a plurality of content distribution servers are DNS round-robin or under the control of a load balancer, they function normally and can be easily deployed as products.
(6) Although it is not a complete delivery destination control method, delivery destination control that is impossible with the current delivery method is possible.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the example of the content delivery by the conventional web server. It is a figure which shows the example of the content delivery by the conventional content delivery server. It is a sequence diagram which shows the example of a content delivery process by the conventional content delivery server. It is a figure which shows the example of data. It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a sequence diagram which shows the process example of embodiment. It is a figure which shows the example of a delivery tag. It is a figure which shows the example of delivery tag verification. It is a figure which shows the example at the time of a JavaScript source return parameter, and a JavaScript source. It is a figure which shows the example of the data acquired by JavaScript execution with a browser. It is a figure which shows the example of JavaScript verification. It is a figure which shows the example of URL verification. It is a figure which shows the example of the content delivered.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Client terminal 11 Browser 2 Network 3 Web server 31 Storage 4 Content delivery server 41 HTTP request receiving part 42 Delivery tag verification part 43 JavaScript generation part 44 Java Script verification part 45 URL verification part 46 Content acquisition part 47 HTTP response transmission part 40 Content storage P Page contents T Distribution tag K1 Private key # 1
K2 private key # 2
UT URL table

Claims (7)

A device that accepts access from a client terminal via a distribution tag included in page content acquired from another server device, and distributes the content to the client terminal,
In response to access from the client terminal via the delivery tag, a code having a function of acquiring information of the server device from which the page content is acquired and assigning content included in the page content is used for verification. A code providing means for providing a signature;
Code verification means for verifying whether or not the code activated by the signature added at the time of access is valid in response to the content allocation access by the code from the client terminal;
Server verification means for verifying whether or not content provision is permitted by the information of the server device from which the page content is acquired when the code verification is normally performed;
A content distribution apparatus comprising: content providing means for providing content to be allocated to the client terminal when server verification is normally performed. The content delivery apparatus according to claim 1,
The content verification apparatus further characterized in that the code verification means further performs time authentication as to whether or not the access is made by a code acquired within a predetermined time from the current time, based on a time stamp added when the code is provided. In the content delivery apparatus as described in any one of Claim 1 or 2,
The signature added by the code providing means includes a content ID that uniquely identifies the content, a domain of the server device that provides the page content, a time stamp indicating the time of processing, a user agent of the accessing client terminal, and A content distribution apparatus that generates a hash algorithm applied to a combination of an IP address and an internal secret key. In the content delivery apparatus as described in any one of Claims 1 thru | or 3,
When accessing via the delivery tag from the client terminal, it is provided with a delivery tag verification means for verifying the validity of the delivery tag based on another signature included in the delivery tag added at the time of access. A feature content distribution apparatus. The content distribution apparatus according to claim 4,
The other signature is generated by applying a hash algorithm to a combination of a content ID that uniquely identifies content, a domain of a server device that provides page content, and another internal secret key. A content distribution apparatus. A method of accepting access from a client terminal via a distribution tag included in page content acquired from another server device and distributing the content to the client terminal,
In response to access from the client terminal via the delivery tag, a code having a function of acquiring information of the server device from which the page content is acquired and assigning content included in the page content is used for verification. A code provision process for providing a signature;
A code verification step for verifying whether or not the code activated by the signature added at the time of access is valid in accordance with the access of the content allocation by the code from the client terminal;
A server verification step of verifying whether or not content provision is permitted by the information of the server device from which the page content is added when accessing the code when the code verification is normally performed;
A content delivery control method comprising: a content providing step of providing content to be allocated to the client terminal when server verification is normally performed. A control program for a device that accepts access from a client terminal via a distribution tag included in page content acquired from another server device and distributes the content to the client terminal,
Computer
In response to access from the client terminal via the delivery tag, a code having a function of acquiring information of the server device from which the page content is acquired and assigning content included in the page content is used for verification. A code providing means for providing a signature;
Code verification means for verifying whether or not the code activated by the signature attached at the time of access is valid in response to the content allocation access by the code from the client terminal;
A server verification means for verifying whether or not content provision is permitted by information of a server device from which the page content is acquired when the code verification is normally performed;
Content providing means for providing content to be allocated to the client terminal when server verification is successfully performed;
A content distribution control program characterized in that it is functioned as:

Images