JP2010086308A - Link generation device and link generation method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To generate a link only to a Web page where generation of a reverse link is intended when a link is made from a Web page provided by an existing Web server. <P>SOLUTION: A link generation device 2 has: a script generating means 21 for generating a link script to a first Web page; a determination means 22 for determining whether or not an access request from a user terminal 1 includes identification information indicating that a link is made from a second Web page linked to the first Web page by using the link script and referrer information; and a link generating means 23 for generating a link to the second Web page inside the first Web page when the access request includes the identification information and the referrer information. The identification information is included in the access request as a part of a link destination address. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a link generation technique for generating a link between Web pages.

  In the Web (World Wide Web), services that provide a plurality of different functions are combined according to the purpose by linking Web pages of different Web sites from Web pages in one Web site using a hyperlink mechanism. Services can be provided. For example, when it is possible to refer to detailed information about a certain thing on one website and a function for sharing written information by users is provided on another website, discussion between users is possible. By linking the web pages of two websites to each other, it is possible to discuss the thing while referring to the detailed information of a certain thing, or to follow the link while discussing the certain thing and refer to the detailed information Become.

  In Non-Patent Document 1, when a link to a web page (page A) of a certain website is established using a mechanism called track back ping, the user's own web page (page B) is sent to the linked partner. A technique is described in which the URL can be linked to page B from page A by notifying the URL.

Also, there is a technique for displaying a link source URL on a Web page by using referrer information issued by a Web browser in HTTP, and establishing a link. Since the URL of the link source web page when the link of a certain web page is clicked and moved to another web page is notified to the link destination as referrer information, the link from the link destination web page to the link source web page Can be stretched.
“TrackBack Technical Specification”, [online], [searched July 28, 2008], Internet <URL: http://www.sixapart.com/pronet/docs/trackback_spec>

  When generating a link between Web pages, it is normally performed by designating the URL of one Web page from the other Web page. In order to be able to refer to each other's Web pages from either Web page, it is necessary to generate a link from both Web pages to the other party.

  In the track back ping of Non-Patent Document 1, a link (reverse link) can be established from one web page to the other web page simply by creating a link from the other web page to the other web page. However, both the web server that provides one web page and the web server that provides the other web page require a mechanism (application) for performing trackback ping. Therefore, it is not possible to form a bi-directional link with a Web server that does not introduce a trackback ping mechanism.

  In addition, when a link is established using referrer information, since a reverse link is established for all URLs of the link source, there is a problem that a link such as spam information is automatically generated.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to a Web page intended to generate a reverse link when linked from a Web page provided by an existing Web server. Only to create links.

  The present invention relates to a link generation device for generating a link, script generation means for generating a link script to a first Web page provided by the link generation device, and a user terminal to the first Web page. When the access request is received, identification information indicating that the access request is linked from the second Web page linked to the first Web page using the link script, and the second link source Determining means for determining whether or not the referrer information indicating the address of the web page is included, and when the access request includes the identification information and the referrer information, Link generating means for generating a link to the second Web page, and the identification information is a part of the link destination address. It is included in the Seth request.

  The present invention is also a link generation method performed by a link generation device, wherein the link generation device includes a script generation step of generating a link script to a first Web page provided by the link generation device, and a user When an access request to the first Web page is received from the terminal, it indicates that the access request is linked from the second Web page linked to the first Web page using the link script. A determination step of determining whether or not identification information and referrer information indicating an address of a link-source second Web page are included; and when the access request includes the identification information and the referrer information And a link generating step for generating a link to the second Web page in the first Web page, and Information is contained in the access request as part of the destination address.

  According to the present invention, when a link is made from a Web page provided by an existing Web server, a link can be generated only for a Web page intended to generate a reverse link.

<First Embodiment>
Hereinafter, a first embodiment of the present invention will be described.

  FIG. 1 is a configuration diagram showing the entire Web system according to the first embodiment of the present invention. The illustrated system has at least one user terminal 1, a Web server A2 (link generation device), and a Web server B3. These devices 1, 2, and 3 are connected to a network 9 such as the Internet. ing.

  In the present embodiment, the Web server A2 is a server that provides, for example, an SNS (Social Networking Service), and a Web site / Web page on which a user can write and discuss predetermined things (themes, topics, etc.). Shall be provided.

  The illustrated web server A2 includes a script generation unit 21, a determination unit 22, a link generation unit 23, an information provision unit 24, and a storage unit 25. The script generation unit 21 generates a link script for linking to a predetermined Web page. When the determination unit 22 receives an access request to the Web page from the user terminal 1, the determination unit 22 determines whether the access request includes identification information to be described later and referrer information indicating the address of the link source Web page. Determine. When the determination unit 22 determines that the identification information and the referrer information are included, the link generation unit 23 generates a link to the link source Web page in the Web page requested to be accessed. The information providing unit 24 provides / transmits content to the user terminal 1.

  The storage unit 25 stores Web page content 26 provided to the user terminal 1 by the Web server A2. The content 26 according to the present embodiment is an HTML file described in HTML (HyperText Markup Language), but is not limited to this, and may be a file described in another language such as XML.

  The Web server B3 is a general Web server, and includes an information providing unit 31 and a storage unit 35. The information providing unit 31 provides and transmits the content (HTML file) 36 stored in the storage unit 35 to the user terminal 1 in response to a request from the user terminal 1. The storage unit 35 stores Web page content (HTML file) 36 provided to the user terminal 1 by the Web server B3.

  The user terminal 1 is, for example, a personal computer or the like, and has a web browser 11.

  As the user terminal 1, Web server A 2, and Web server B 3 described above, for example, a general-purpose computer system including at least a CPU, a memory, and an external storage device such as an HDD can be used. In this computer system, each function of each device is realized by the CPU executing a predetermined program loaded on the memory. For example, the functions of the user terminal 1, the Web server A2, and the Web server B3 are as follows. The CPU of the user terminal 1 is a program for the user terminal 1, and the Web server A2 is a program for the Web server A2. When the CPU is a program for the Web server B3, the CPU of the Web server B3 executes the program. The user terminal 1, Web server A2, and Web server B3 may include an input device and an output device as necessary.

  Next, the operation of the system of this embodiment will be described.

  2 and 3 are sequence diagrams showing the operation of the system of this embodiment. As shown in FIG. 2, the Web browser 11 of the user terminal 1 receives a user (user) instruction and receives a predetermined Web page (hereinafter referred to as “Web page A (first Web)” provided by the Web server A2. Request to access the page) ") (S11). The access request includes the address (URL or the like) of Web page A, and the user inputs or clicks the address of Web page A using an input device such as a keyboard or a mouse.

  Note that communication between the user terminal 1 and the Web server A2 and Web server B3 is performed using HTTP (HyperText Transfer Protocol) or the like.

  When receiving the access request, the script generating unit 21 of the Web server A2 generates a link script for generating a link to the Web page A based on the transmitted address. Further, the script generation unit 21 reads out the HTML file for the Web page A (hereinafter, “HTML file A”) from the storage unit 25 based on the transmitted address, and generates the link script generated in the read HTML file A. The link script is displayed on the Web page A (S12). Then, the information providing unit 24 of the Web server A2 transmits the HTML file A of the Web page A updated by adding the link script to the user terminal 1 (S13).

  The Web browser 11 of the user terminal 1 receives the HTML file A of the Web page A to which the link script is added, and displays the Web page A in which the link script is described on the display (S14).

  FIG. 4 shows an example of the web page A displayed on the user terminal 1. On the illustrated web page A, a link script 41 shown below is displayed.

<a href = “http://a.jp/pagea/xxx?id=x”>
<img src = “http://a.jp/linkimage.png” />
</a>
In the above link script, a link destination address and a display image are described by an <a> tag. The link destination address is described using the “href” attribute. The script generation unit 21 of the present embodiment uses a link obtained by adding identification information (id = x) to the address (http://a.jp/pagea/xxx) of the Web page A specified in the access request. Set as the destination address (http://a.jp/pagea/xxx?id=x).

  The identification information is information for identifying whether or not the web page linked by using the link script generated by the script generation unit 21 is accessed, and is added as a part of the link destination address. In the example shown in the figure, as identification information, a parameter that can be delivered to a linked Web server by a mechanism such as CGI (Common Gateway Interface) (a value x is set for an argument named id) is used. Yes. However, the present invention is not limited to this, and if the format is based on the URL scheme, the identification information may be set by various methods such as inserting a parameter in the URL path.

  Even if you specify "http://a.jp/pagea/xxx" and access, "http://a.jp/pagea/xxx?id=x" with identification information added Even when access is specified, the HTML file A transmitted to the user terminal 1 is the same, and the same Web page A is displayed on the user terminal 1. However, they differ in whether or not identification information is added.

  The display image is described using the “img” attribute, and in the illustrated example, an address (http://a.jp/linkimage.png) where the display image is stored is described.

  The user browses the Web page A displayed on the user terminal 1. Then, the user has the content of a predetermined Web page (hereinafter, “Web page B (second Web page)”) stored in the Web server B3 managed and operated by the user and the content of the Web page A. When it is desired to allow other users who have accessed Web page B to access related Web page A, a link to Web page A is generated in Web page B using link script 41. (S15). In this case, it is assumed that the user has the authority to edit the content of Web page B.

  More specifically, the user copies and pastes the link script 41 displayed on the web page A, for example, so that the link script 41 is stored in the web server B3 HTML file (hereinafter referred to as the HTML file for the web page B). , “HTML file B”). Thereby, the HTML file B for the web page B stored in the storage unit 35 of the web server B3 is updated (S16).

  2 is described in the HTML file B for the Web page B described above, and then the process shown in FIG. 3 is performed.

  The user of the user terminal 1 inputs an operation instruction (such as input or click of an address) for accessing the Web page B of the Web server B3 to the user terminal 1. Note that the user here may be the user shown in FIG. 2 (the user who has the authority to edit the content of Web page B) or another user.

  The web browser 11 of the user terminal 1 receives the user's instruction and transmits an access request to the web page B provided by the web server B3 (S21). The information providing unit 31 of the Web server B3 reads the HTML file B corresponding to the address of the Web page B specified by the access request from the storage unit 35, and transmits the read HTML file B to the user terminal 1 (S22). . The web browser 11 of the user terminal 1 receives the HTML file B and displays the web page B (S23).

  FIG. 5 shows an example of the Web page B displayed on the user terminal 1. The HTML file B is updated in S16 of FIG. 2, and the updated HTML file B is described in a link script with the link destination as the Web page A. As a result, on the illustrated web page B, the display image 42 (link) that is the logo mark of the web page A is displayed. The display image 42 is associated with address information (http://a.jp/pagea/xxx?id=x) of the linked Web page A described in the link script.

  The user follows the link to the Web page A by clicking the display image 42 of the Web page B displayed on the user terminal 1. The web browser 11 of the user terminal 1 accepts a user operation instruction (S24) and links to the web page A (S25). That is, the Web browser 11 transmits an access request to the Web server A2 with the address of the Web page A associated with the display image 42 as a destination.

  The access request includes a link destination address (http://a.jp/pagea/xxx?id=x) described in the link script and referrer information. The referrer information is information issued by the web browser 11. The referrer information of this embodiment is set with the address of the link source web page when linking (moving) from one web page to another. . In the case of FIG. 5, the Web browser 11 transmits the address (http://b.jp/index.html) of the Web page B as referrer information.

  When receiving a link access request, the determination unit 22 of the Web server A2 determines whether the access request satisfies the following two conditions (S26).

  The first condition is that identification information is added to the link destination address included in the access request. In this embodiment, it is determined whether or not the identification information in which the value of x is set for the parameter variable id is added to the link destination address. When identification information is added to the link destination address, it is possible to determine that the access request is an access request by following the link (display image 42) displayed by the link script generated in FIG. The second condition is that referrer information is included in the access request.

  When the first and second conditions are satisfied, that is, when the identification information is added to the link destination address included in the access request and the referrer information is included in the access request, the link generation unit 23 A link to the link source Web page B is generated in the link destination Web page A (S27).

  That is, the link generation unit 23 reads the HTML file A of the Web page A from the storage unit 25, and updates the HTML file A so that the link to the Web page B is displayed in the Web page A based on the referrer information. Then, the information providing unit 24 transmits the updated HTML file A to the user terminal 1 (S28).

  The web browser 11 of the user terminal 1 receives the updated HTML file A and displays the web page A including the link to the web page B on the display (S29).

  FIG. 6 shows an example of the updated web page A displayed on the user terminal 1. In the illustrated Web page A, a link 43 to the Web page B that is the link source is displayed. When the user clicks the link 43 to the Web page B displayed on the user terminal 1, the user can link to the Web page B.

  In the first embodiment described above, the Web server A2 provides a link script to its own Web page A, and the Web page B generates a link to the Web page A using the link script. Then, when the web server A2 traces this link from the web page B and accesses the web page A, the web server A2 generates a link in the web page A to the link source web page B using the referrer information.

  As a result, in the Web server A2 of the first embodiment, when a link is made from a Web page provided by the existing Web server B, a link is generated only for the Web page intended to generate a reverse link. be able to.

  Further, the Web server B of the first embodiment is an existing general Web server. That is, in the above embodiment, a bidirectional link with the Web server A2 can be formed without introducing an application such as trackback ping on the Web server B3 side. That is, it is possible to realize interactive seamless content cooperation between the Web page of the Web server A2 and the Web page of the existing Web server B.

  Further, in the first embodiment, by adding identification information to the link destination address of the link script generated by the Web server A2, the Web server A2 is the link intended by itself (that is, generated by itself). A link using a link script) and a bi-directional link can be formed with the link source Web page.

<Second Embodiment>
Hereinafter, a second embodiment of the present invention will be described.

  In this embodiment, a function for performing user authentication by the Web server A2 is added to the first embodiment.

  FIG. 7 is a system configuration diagram of the present embodiment. The Web server A2 of the present embodiment is different from the system configuration of the first embodiment (see FIG. 1) in that it further includes an authentication unit 27, and is otherwise the same as the first embodiment. Upon receiving a web page access request from the user terminal 1, the authentication unit 27 requests authentication information from the user terminal 1 and authenticates whether the received authentication information is valid authentication information.

  Next, the operation of the system of this embodiment will be described.

  8 and 9 are sequence diagrams showing the operation of the system of this embodiment. As shown in FIG. 7, the web browser 11 of the user terminal 1 receives a user instruction and transmits an access request to the web page A provided by the web server A2 (S31). The access request includes the address of Web page A.

  When receiving the access request, the authentication unit 27 of the Web server A2 requests authentication information such as a user ID and a password from the user terminal 1 (S32). The web browser 11 of the user terminal 1 receives the authentication information input by the user and transmits it to the web server A (S33). Upon receiving the authentication information, the authentication unit 27 authenticates whether or not the authentication information is a valid user (S34). For example, the authentication unit 27 determines that the authentication information is legitimate authentication information when information that matches the received authentication information exists in the authentication information storage unit (not shown).

  If it is determined that the authentication information is valid, the script generation unit 21 generates a link to the Web page A based on the address transmitted in the access request in S31 and the authentication information transmitted in S32. A link script is generated (S35).

  The link script of this embodiment is different from that of the first embodiment in that authentication information is used as identification information added to a link destination address. That is, the script generation unit 21 according to the present embodiment adds, for example, a user ID (id = user11) to the address (http://a.jp/pagea/xxx) of the Web page A specified in the access request. Is set as the link destination address (http://a.jp/pagea/xxx?id=user11). For example, the script generation unit 21 generates the following link script.

<a href = “http://a.jp/pagea/xxx?id=user11”>
<img src = “http://a.jp/linkimage.png” />
</a>
The authentication information used for the identification information is not limited to the user ID, but may be any information that can identify the user (user identification information). It may be a thing.

  Then, based on the transmitted address, the script generation unit 21 reads the HTML file A for the Web page A from the storage unit 25, adds the generated link script to the read HTML file A, and on the Web page A Display the link script. Then, the information providing unit 24 transmits the HTML file A of the web page A updated by adding the link script to the user terminal 1 (S36).

  Since the subsequent processing from S37 to S39 is the same as the processing of the first embodiment (FIG. 2: S14 to S16), the description thereof is omitted here.

  After the link script 41 with the Web page A as the link destination is described in the HTML file B for the Web page B by the process of FIG. 8 described above, the process shown in FIG. 9 is performed. The user in FIG. 9 is assumed to be the same user as the user in FIG. 8 (a user who has the authority to edit the content of the Web page B).

  The web browser 11 of the user terminal 1 receives the user's instruction and transmits an access request to the web page B provided by the web server B3 (S51). The information providing unit 31 of the Web server B3 reads out the HTML file B corresponding to the address of the Web page B specified in the access request from the storage unit 35, and transmits the read HTML file B to the user terminal 1 (S52). . The web browser 11 of the user terminal 1 receives the HTML file B and displays the web page B (see FIG. 5) (S53).

  The user follows the link to the Web page A by clicking the link 42 of the Web page B displayed on the user terminal 1. The web browser 11 of the user terminal 1 accepts a user operation instruction (S54) and links to the web page A (S55). That is, the Web browser 11 transmits an access request to the Web server A2 with the address of the Web page A associated with the display image 42 as a destination.

  In this access request, the link destination address (http://a.jp/pagea/xxx?id=user11) described in the link script and the referrer information (the address of the link source Web page B: http: //b.jp/index.html).

  When receiving the access request, the authentication unit 27 of the Web server A2 requests authentication information from the user terminal 1 (S56). The web browser 11 of the user terminal 1 receives the authentication information input by the user and transmits it to the web server A (S57). Upon receiving the authentication information, the authentication unit 27 authenticates whether or not the authentication information is valid user authentication information (S58).

  If it is determined that the authentication information is valid, the determination unit 22 determines whether the access request satisfies the following two conditions (S59).

  The first condition is that identification information is added to the link destination address included in the access request, and that the identification information matches the authentication information transmitted in S57. In the present embodiment, it is determined whether or not the user ID set as the identification information of the link destination address matches the user ID transmitted in S57. If they match, the access request is an access request by the same user who made the access request to Web page A in FIG. 8 following the link displayed by the link script generated in FIG. Can be determined. The second condition is that referrer information is included in the access request.

  When the first and second conditions are satisfied, that is, when the identification information of the link destination address matches the user ID and the referrer information is included in the access request, the link generation unit 23 is the link destination. In the Web page A, a link to the link source Web page B is generated (S60). Then, the information providing unit 24 transmits the updated HTML file A to the user terminal 1 (S61). The web browser 11 of the user terminal 1 receives the updated HTML file A and displays the web page A including the link to the web page B on the display (S62).

  In the second embodiment, user identification information such as a user ID is used as identification information for a link script generated by the Web server A2. Thus, the reverse link is not generated unless the user who added the link script to the HTML file B of the Web server B3 follows the link. Specifically, when a user creates a link to Web page A on Web page B, a link to Web page B is generated once by clicking to test whether the link is correctly formed. Then, after that, another user can also refer to the link and follow the link to the Web page B. As a result, it is possible to prevent generation of a reverse link such as spam, which is not intended by the user or service operator.

<Third Embodiment>
Hereinafter, a third embodiment of the present invention will be described.

  In the present embodiment, the Web server A2 has a function for displaying the summary information of the Web server B3 in the Web page A together with the link of the link source Web server B3 in the first embodiment.

  FIG. 10 is a system configuration diagram of this embodiment. The Web server A2 of this embodiment is different from the system configuration of the first embodiment (see FIG. 1) in that it further includes a summary information acquisition unit 28, and is otherwise the same as that of the first embodiment. The summary information acquisition unit 28 acquires summary information from the link source Web server B3 based on the referrer information included in the access request.

  Next, the operation of the system of this embodiment will be described.

  In the present embodiment, first, the same processing as in FIG. 2 of the first embodiment is performed. Since the processing of FIG. 2 has been described in the first embodiment, the description thereof is omitted here. After the link script 41 with the Web page A as the link destination is described in the HTML file B for the Web page B by the processing of FIG. 2, the processing shown in FIG. 11 is performed.

  Since S71 to S76 of FIG. 11 are the same as S21 to S26 of FIG. 3 of the first embodiment, description thereof is omitted here. When the determination unit 22 of the Web server A2 determines that the identification information is added to the link destination address included in the access request and the referrer information is included in the access request (S76), the summary information acquisition 28 Specifies the summary information address where the summary information is stored based on the referrer information, and requests the summary information from the summary information address (S77).

  Specifically, it is assumed that the address (http://b.jp/index.html) of the Web page B3 is set in the referrer information (link source address). The summary information is generally stored in an “RSS file” or “RDF file” around the link source address. Therefore, the summary information acquisition unit 28 refers to the link source address of the referrer information or an address indicating the surrounding directory, and sets the link source address to “http://b.jp/index.rss” or “http: / /b.jp/index.rdf ", and requests summary information from the Web page B3 with the converted address as the destination.

  The information providing unit 31 of the Web page B3 transmits the “RSS file” or “RDF file” to the Web page A2 (S78).

  The link generation unit 23 generates a link to the link source Web page B in the link destination Web page A and also generates summary information based on the “RSS file” or the like (S79).

  That is, the link generation unit 23 reads the HTML file A of the Web page A from the storage unit 25, and summarizes the information in the Web page A based on the link to the Web page B based on the referrer information and the “RSS file”. Update HTML file A to display. Then, the information providing unit 24 transmits the updated HTML file A to the user terminal 1 (S80).

  The Web browser 11 of the user terminal 1 receives the updated HTML file A, and displays the Web page A including the link to the Web page B and summary information on the display (S81).

  FIG. 12 shows an example of the updated web page A displayed on the user terminal 1. In the illustrated web page A, summary information 44 of the web page B is displayed together with a link 43 to the web page B that is the link source. The user can link to the Web page B by clicking the link 43 to the Web page B after recognizing the contents of the Web page B from the summary information 44. Note that the function of displaying the summary information of this embodiment may be added to the second embodiment.

  The present invention is not limited to the first, second, and third embodiments described above, and various modifications are possible within the scope of the gist. For example, in the above embodiment, the link script provided by the Web server A2 only displays the display image (link) 42 associated with the link destination address of the Web server A (see FIG. 5). However, the Web server A2 may generate a link script that displays not only the display image (link) 42 but also other information. Specifically, when the content (HTML file B) to which the link script is pasted is displayed on the user terminal 1, new information, latest summary information, etc. of the Web server A2 are automatically sent from the Web server A2 ( Alternatively, it may be acquired periodically and displayed together with the display image (link) 42. By doing so, it is possible to show the new information and the latest summary information of the Web page A to the user who has referred to the Web page B, and prompt the user to access the Web page A.

1 is an overall configuration diagram of a system according to a first embodiment of the present invention. It is a sequence diagram which shows operation | movement of 1st Embodiment. It is a sequence diagram which shows operation | movement of 1st Embodiment. It is a figure which shows an example of the screen of the web page A of 1st Embodiment. It is a figure which shows an example of the screen of the web page B of 1st Embodiment. It is a figure which shows an example of the screen of the web page A of 1st Embodiment. It is a whole block diagram of the system which concerns on the 2nd Embodiment of this invention. It is a sequence diagram which shows operation | movement of 2nd Embodiment. It is a sequence diagram which shows operation | movement of 2nd Embodiment. It is a whole block diagram of the system which concerns on the 3rd Embodiment of this invention. It is a sequence diagram which shows operation | movement of 3rd Embodiment. It is a figure which shows an example of the screen of the web page A of 3rd Embodiment.

Explanation of symbols

1 User terminal 11 Web browser 2 Web server A
21 Script generation part 22 Discrimination part 23 Link generation part 24 Information provision part 25 Storage part 26 Content (HTML file A)
27 Authentication Unit 28 Summary Information Acquisition Unit 3 Web Server B
31 Information Providing Unit 35 Storage Unit 36 Content (HTML File B)

Claims (10)

A link generation device for generating a link,
Script generation means for generating a link script to the first Web page provided by the link generation device;
When an access request to the first web page is received from the user terminal, the access request is linked from the second web page linked to the first web page using the link script. Discriminating means for discriminating whether or not the identification information indicating the address and the referrer information indicating the address of the second web page of the link source are included;
Link generating means for generating a link to a second Web page in the first Web page when the identification information and the referrer information are included in the access request;
The link generation device, wherein the identification information is included in the access request as a part of a link destination address. The link generation device according to claim 1,
User identification information is used for the identification information. The link generation device according to claim 2,
It further has an authentication means for acquiring user identification information from the user terminal and performing user authentication,
The determination means determines whether or not the identification information included in the access request matches the user identification information acquired by the authentication means,
The link generation unit generates a link to a second Web page in the first Web page when the identification information matches the user identification information. The link generation device according to any one of claims 1 to 3,
Further comprising summary information acquisition means for acquiring summary information of the link source second Web page based on the referrer information included in the access request;
The link generation unit generates the summary information together with a link to a second Web page in the first Web page. The link generation device according to any one of claims 1 to 4,
The script generation means generates a link script to the first Web page provided by the link generation device, and generates a script for displaying summary information of the first Web page. apparatus. A link generation method performed by a link generation device,
The link generation device includes:
A script generation step for generating a link script to the first Web page provided by the link generation device;
When an access request to the first web page is received from the user terminal, the access request is linked from the second web page linked to the first web page using the link script. A determination step of determining whether or not the identification information indicating the address and the referrer information indicating the address of the link source second Web page are included;
When the access request includes the identification information and the referrer information, a link generation step of generating a link to the second Web page in the first Web page is performed.
The link generation method, wherein the identification information is included in the access request as a part of a link destination address. The link generation method according to claim 6,
A link generation method using user identification information as the identification information. The link generation method according to claim 7,
Acquiring user identification information from the user terminal and further performing an authentication step for user authentication,
The determining step determines whether or not the identification information included in the access request matches the user identification information acquired by the authentication unit;
The link generation step generates a link to a second Web page in the first Web page when the identification information matches the user identification information. A link generation method according to any one of claims 6 to 8, comprising:
Based on the referrer information included in the access request, a summary information acquisition step of acquiring summary information of the second web page of the link source is further performed,
The link generation step generates the summary information together with a link to the second Web page in the first Web page. The link generation method according to any one of claims 6 to 9,
The script generation step generates a link script to the first Web page provided by the link generation device, and generates a script for displaying summary information of the first Web page. Method.

Images