JP5943991B2 - Web server with file accidental deletion prevention program and file accidental deletion prevention function - Google Patents

Description

The present invention provides an erroneous file deletion prevention program and an erroneous file deletion prevention function for preventing a related file called from another markup document from being accidentally deleted when deleting a markup document such as an HTML file. The present invention relates to a provided web server.

  A Web server that provides various information on the Internet is designated as a markup document, which is a file described in a markup language such as HTML or XML, used when displaying a Web page, and a markup document. Stored are related files such as an image file for displaying an image and an include file such as JavaScript (registered trademark), which are called when a Web page is displayed. When a user operates a network terminal such as a personal computer or a smartphone to start a Web browser and calls a markup document from a Web server, the related files specified in the markup document are also called, and these files are used for Web The page is displayed on the network terminal.

  The related file called by the markup document may include general-purpose files used for various Web pages. Such a related file is stored in the Web server for each markup document corresponding to each Web page. There are cases in which multiple markup documents are shared rather than stored.

  In such cases, when deleting one markup document, the related file called by the markup document is often deleted at the same time, and the deleted related file is also used by other markup documents. If a related file is included, the related file deleted when another markup document is called cannot be called, and there is a problem that a Web page cannot be displayed properly. is there.

  As a technique for appropriately managing actions such as update and deletion of a file and accompanying files accompanying the file, actions for the accompanying file when updating the file are set in advance corresponding to the file, and when the file is updated An invention that automatically executes a set action on an accompanying file is disclosed (see Patent Document 1).

JP 2005-189946 A

  In order to deal with the problem that related files used in other markup documents are deleted when the markup document is deleted, the markup document is deleted as in the invention described in Patent Document 1. It may be possible to set actions such as deletion of related files for each markup document and related files, but if you try to do so, you will need to perform actions individually for all markup documents and each related file. In addition to being required to set, when new markup documents are saved or other markup documents are deleted, the sharing relationship of related files with other markup documents is reviewed. If necessary, resetting must be performed, and file management is assumed to be inefficient.

The present invention has been made to cope with such problems. When a markup document such as an HTML file is deleted, a related file called from another markup document is erroneously deleted. It is an object of the present invention to provide a web server provided with an erroneous file deletion prevention program and an erroneous file deletion prevention function.

  The present invention for solving such a problem includes a markup document for displaying a Web page, a file storage unit for storing a related file called from the markup document, and each markup stored in the file storage unit. When deleting a markup document in a Web server having a file information storage unit that stores information related to a related file called from a document, the related file called from another markup document is prevented from being deleted by mistake. An erroneous file deletion prevention program, wherein a deletion request reception step for receiving a deletion request for a markup document to the Web server, and a related file called from the markup document for which the deletion request has been received in the deletion request reception step Search the information storage unit and find other A file identification step that identifies a related file that is also called from a backup document, a markup document that has received a deletion request in the deletion request reception step, and a call from the markup document excluding the related file that is identified in the file identification step And a file deletion step of deleting a related file from the file storage unit.

  In the present invention, information related to the related file called by each markup document is stored in the file information storage unit, and when deleting one markup document, another markup document is referred to by referring to the file information storage unit. By configuring the related files used in the document to be excluded from the deletion target, it is possible to efficiently prevent the erroneous deletion of the related files. The markup document according to the present invention corresponds to a file for displaying a Web page described in a markup language such as HTML or XML.

  Further, the present invention includes a file storage step of archiving all or part of the markup document and related files deleted from the file storage unit in the file deletion step in the Web server and storing them in a file storage unit. It can also be made to perform.

  According to the present invention, it is possible to efficiently prevent erroneous deletion of related files. However, according to this aspect, since the deleted markup document and related files are archived, the markup document itself is erroneously deleted. If you do, you can restore it including the necessary related files.

  Further, the present invention is a method of accepting an upload of a new markup document and a related file to be called from the markup document to the Web server, and being called from the markup document that has been uploaded in the upload acceptance step. , If there is a related file that is not included in the related file accepted for upload in the upload reception step, search the file information storage unit for whether it is included in the related file called from another markup document, If it is not included in the related file called from other markup documents, the upload requesting the upload of the related file not included in the related file received in the upload receiving step. And determined step may be characterized in that for the execution.

  In this aspect, when simultaneously uploading a new markup document and a related file, the file information storage unit is referred to, the necessary related file is not included, and the related file may be another markup document. When not used, the user is prompted to upload the related file to prevent the Web page from being appropriately displayed due to the absence of the related file.

  Further, the present invention provides the Web server with an upload reception step for receiving a new markup document and an upload of a related file called from the markup document, and a relationship called from the markup document for which the upload has been received at the upload reception step. The file information storage unit is searched for whether the file is included in a related file called from another markup document, and the related file included in the related file called from another markup document is specified. 2 of the file identification step, the markup document accepted for upload in the upload acceptance step, and the related file accepted for upload in the upload acceptance step, identified in the second file identification step Related files except the relevant file was called from another markup document, and file storage step of storing in the file storage unit may be characterized in that for the execution.

  According to this aspect, when simultaneously uploading a new markup document and a related file, with reference to the file information storage unit, if a related file that is also used in other markup documents is included, Since the configuration does not store duplicate related files, effective use of resources of the Web server can be promoted.

  Furthermore, the present invention relates to an upload reception step for accepting upload of a new markup document to the Web server, and a related file called from the markup document accepted for upload in the upload acceptance step from other markup documents. An upload requesting step is executed to search the file information storage unit for whether it is not included in the related file to be called and to request uploading of the related file not included in the related file called from another markup document. This may be a feature.

  According to this aspect, when only a new markup document is uploaded, the file information storage unit is referred to prompt the upload of the related file that is not used in other markup documents among the necessary related files. , It is possible to efficiently upload related files necessary for properly displaying a Web page.

  The present invention can also be specified as a method for preventing erroneous file deletion executed by the erroneous file deletion prevention program according to the present invention.

  The method for preventing erroneous file deletion according to the present invention includes a markup document for displaying a Web page, a file storage unit for storing a related file to be called from the markup document, and each mark stored in the file storage unit. Prevents accidental deletion of related files called from other markup documents when a markup document is deleted in a Web server having a file information storage unit that stores information related to related files called by the uploaded document And a deletion request reception step in which the Web server receives a deletion request for a markup document, and a markup document in which the Web server has received a deletion request in the deletion request reception step. For the related file to be called, A file specifying step of searching a file information storage unit to specify a related file called from another markup document, the markup document that the Web server has received a deletion request in the deletion request receiving step, And a file deletion step of deleting a related file called from the markup document excluding the related file specified in the file specifying step from the file storage unit.

  The method for preventing erroneous file deletion according to the present invention can also be specified as a method for preventing erroneous file deletion corresponding to each aspect of the file erroneous deletion prevention program according to the present invention described above.

  The present invention can also be specified as a Web server having a function for preventing erroneous file deletion by the program for preventing erroneous file deletion according to the present invention.

  A Web server having an erroneous file deletion prevention function according to the present invention prevents an erroneous file deletion prevention function that prevents a related file called from another markup document from being deleted by mistake when deleting a markup document. A markup document for displaying a Web page, a file storage unit for storing a related file called from the markup document, and a markup document stored in the file storage unit. File information storage means for storing information relating to the related file to be called; a deletion request receiving means for receiving a deletion request for the markup document; and the related file to be called from the markup document for which the deletion request receiving means has received the deletion request. Search the information storage means to find other markup A file specifying unit for specifying a related file called from a document; a markup document for which the deletion request receiving unit has received a deletion request; and a related file to be called from the markup document excluding the related file specified by the file specifying unit. And a file deletion unit that deletes the file from the file storage unit.

  Further, the Web server provided with the erroneous file deletion prevention function according to the present invention is specified as the Web server provided with the erroneous file deletion prevention function corresponding to each aspect of the file erroneous deletion prevention program according to the present invention described above. You can also

  According to the present invention, when a markup document such as an HTML file is deleted, it is possible to efficiently prevent a related file called from another markup document from being erroneously deleted. Also, when uploading a new markup document, it is effective in preventing Web pages from being displayed properly because there is no necessary related file, and promoting effective use of Web server resources. is there.

It is a figure which shows the outline | summary of embodiment of this invention. It is a block diagram which shows an example of a structure of the web server provided with the file erroneous deletion prevention program which concerns on this invention. It is a figure which shows an example of the information memorize | stored in the file information storage part of the web server provided with the file erroneous deletion prevention program which concerns on this invention. It is a flowchart which shows the processing flow at the time of the HTML file deletion of the file erroneous deletion prevention program which concerns on this invention. It is the figure which showed an example of the processing method of the related file at the time of the file deletion by this invention. It is the figure which showed two examples of the update method of the information memorize | stored in the file information storage part at the time of the file deletion by this invention. It is a 1st flowchart which shows the processing flow at the time of uploading of the new HTML file of the file erroneous deletion prevention program which concerns on this invention. It is a 2nd flowchart which shows the processing flow at the time of the upload of the new HTML file of the file erroneous deletion prevention program which concerns on this invention. It is the 1st figure which showed an example of the processing method of the related file at the time of the upload of the new HTML file by this invention. It is the 2nd figure which showed an example of the processing method of the related file at the time of the upload of the new HTML file by this invention.

  Embodiments for carrying out the present invention will be described below in detail with reference to the drawings. The following description shows an example of an embodiment of the present invention. Embodiments such as a language used in a markup document, a type of a related file, and a data format of a file information storage unit are shown below. However, the present invention is not limited to the examples.

  FIG. 1 shows an example of an embodiment of the present invention. A user who operates a user terminal that is a network terminal that can be connected to the Internet, such as a personal computer, a smartphone, or a tablet computer, starts a Web browser on the user terminal, connects to the Internet, accesses a Web server, and displays a Web page. Various information can be acquired by browsing.

  A Web page called from a Web server displays a markup document that is a file described in a markup language such as HTML or XML, and an image that is called when a Web page is specified by the markup document and displayed. Displayed by image files and related files such as include files such as JavaScript (registered trademark), and files for displaying these Web pages are stored in the Web server. When the Web server receives a request specifying a URL from the user terminal, a corresponding markup document (in the following example, an HTML file) and a related file are called up by the user terminal.

  In the present invention, information related to such HTML files and related files called by the respective HTML files is managed in the file management database, and necessary related files are prevented from being accidentally deleted. Specifically, when an HTML file is deleted, the file management database confirms whether the related file called by the deleted HTML file is a related file that is also used in another HTML file, and the other HTML If there is a related file that is also used in the file, exclude it from the deletion target.

  In addition, when a new HTML file is uploaded, it is checked whether necessary related files including related files used in other HTML files exist, and related files that do not exist are confirmed. Requests upload to the user terminal. Further, when the uploaded related file is also used in another HTML file, the uploaded related file is excluded from the storage target, thereby promoting effective use of the resources of the Web server.

  FIG. 2 shows an example of the configuration of a Web server provided with a file erroneous deletion prevention program according to the present invention. The file erroneous deletion prevention program according to the present invention is provided in the Web server 10, but the physical configuration of the computer constituting the Web server 10 is not particularly limited. It may be configured as a function of a unit, or may be configured by a plurality of computers.

  The Web server 10 includes an auxiliary storage device such as a CPU, a main memory, and an HDD, and is configured by a computer connected to the Internet. In order to realize a predetermined function, each Web server 10 is stored in an auxiliary storage device such as an HDD. An application program corresponding to the function is read into the main memory or the like, and the CPU executes arithmetic processing using the main memory or the like as a working area.

  The Web server 10 includes a Web page output unit 14 and a file management unit 15, all of which are functionally specified, and each function is stored in an auxiliary storage device such as an HDD. It is realized by reading an application program corresponding to each stored function into a main memory or the like and executing arithmetic processing by the CPU using the main memory or the like as a working area.

  In addition, the Web server 10 is provided with an HTML file storage unit 11, a related file storage unit 12, a file information storage unit 13, and a file storage unit 16, each of which is a predetermined storage of an auxiliary storage device such as an HDD. Space is allocated.

  The administrator terminal 20 is a computer connected to the Web server 10 that can delete a file stored in the Web server 10 and upload a file to the Web server 10, but its configuration is particularly limited. is not. The administrator terminal 20 and the Web server 10 may be connected via the Internet.

  The user terminal 30 may be a network terminal equipped with a web browser such as a personal computer, a smartphone, or a tablet computer that can be connected to the Internet.

  When a user who wants to browse a web page starts up a web browser on the user terminal 30 and connects to the web server 10 to request the URL of the web page he wants to browse, the web server 10 starts up the web page output unit 14 and HTML. The HTML file of the Web page specified by the URL is called from the file storage unit 11 and the related file such as the image file or the include file specified in the HTML file is called from the related file storage unit 12, and these files are called the user terminal. Reply to 30. In the user terminal 30, the web browser reads these files and displays a web page corresponding to the requested URL.

  When the administrator of the Web page wants to delete an HTML file or upload a new HTML file, the administrator terminal 20 designates the file to be deleted or transmits the file to be uploaded from the administrator terminal 20 to the Web server 10. . In the Web server 10, the file management unit 15 is activated to check the information stored in the file information storage unit 14 (the file management unit 15 and the file information storage unit 14 correspond to the file management database in FIG. The specific configuration is not particularly limited), specify related files that should not be deleted together with HTML files, related files that are missing at the time of uploading, related files that do not need to be saved because they overlap, and HTML Processing such as deleting files stored in the file storage unit 11 and the related file storage unit 12 and uploading files to the HTML file storage unit 11 and the related file storage unit 12 is executed.

  FIG. 3 shows an example of information stored in the file information storage unit 13, and each HTML file stored in the HTML file storage unit 11 is stored in the related file storage unit 12 called from the HTML file. Information for specifying the related file is stored.

  In the example of FIG. 3, the flag “1” indicates that the related file is used, and the flag “0” is not used. From the HTML file “A.html”, “A.gif” “ The related files of “A.js” and “A.css” are called from the “B.html” HTML file, and the related files of “B.gif”, “A.js”, and “B.css” are respectively called A web page is displayed. Among these related files, “A.js” can be confirmed to be shared by both HTML files.

  Based on the above configuration, the processing flow when deleting an HTML file and the processing flow when uploading an HTML file of the erroneous file deletion prevention program according to the present invention will be described below.

  The flowchart of FIG. 4 shows a processing flow at the time of HTML file deletion of the erroneous file deletion prevention program according to the present invention, FIG. 5 shows an example of a related file processing method at the time of file deletion, and FIG. Two examples of the method of updating the information stored in the file information storage unit are shown. The processing flow when deleting an HTML file will be described using these examples.

  When the Web server 10 receives a request for deleting an HTML file stored in the HTML file storage unit 11 from the administrator terminal 20 (S01), the file management unit 15 is activated and the related file called from the HTML file that has received the deletion request Is specified (S02). The related file may be specified from the information stored in the file information storage unit 13 shown in the example of FIG. 3, or the HTML file to be deleted is called from the HTML file storage unit 11 and the HTML file is read out. It may be read.

  Next, the information in the file information storage unit 13 is searched for each related file called from the HTML file to be deleted (S03), and the related file shared with the other HTML file, that is, another HTML file. It is confirmed whether there is a related file called from the file (S04).

  When there is a related file called from another HTML file, the HTML file to be deleted is called from the HTML file storage unit 11 and from other HTML files among the related files called from the HTML file to be deleted. The related files excluding the related files are deleted from the related file storage unit 12 respectively. It should be noted that the HTML file to be deleted and all or part of the related file are archived so that it can be restored including the related file when the HTML file is accidentally deleted, and the file storage unit 16 (S05).

  FIG. 5 shows an example of such a case. HTML files “A.html” and “B.html” using the related files shown in the example of FIG. 3 are stored in the HTML file storage unit 11. Assume that a request to delete the HTML file “A.html” is received.

  When the file information storage unit 13 is searched, among the related files of “A.gif”, “A.js”, and “A.css”, “A.js” is related to the HTML file of “B.html”. Since the file, that is, the related file called from the HTML file of “B.html” can be specified, the HTML file of “B.html” is called by excluding “A.js” from the deletion target. In this case, it is possible to avoid a situation in which “A.js” has been deleted and the Web page is not displayed.

  When the HTML file and the related file are deleted as in the example of FIG. 5, the information stored in the file information storage unit 13 is updated as shown in the example of FIG. The lower left of FIG. 6 shows an example of archiving the deleted HTML file and related files. The record of the deleted related file is not deleted, and a flag “9” indicating that it has been deleted is set. In the case where the deleted HTML file and the related file are not archived, the record of the deleted related file may be deleted as in the example shown in the lower right of FIG.

  Returning to the flowchart of FIG. 4, when there is no related file called from another HTML file, the HTML file to be deleted is deleted from the HTML file storage unit 11 and all the files to be called from the HTML file to be deleted are deleted. The related file is deleted from the related file storage unit 12. Even in this case, it is desirable that all or a part of the HTML file to be deleted and the related file are archived and stored in the file storage unit 16 (S06).

  The flowcharts of FIGS. 7 and 8 show two patterns of processing flow at the time of uploading a new HTML file of the erroneous file deletion prevention program according to the present invention, and FIGS. 9 and 10 are diagrams at the time of uploading a new HTML file. Two examples of the related file processing method are respectively shown. The processing flow at the time of uploading a new HTML file will be described using these examples.

  In the processing flow of FIG. 7, it is assumed that a new HTML file and a related file are simultaneously uploaded from the administrator terminal 20. When uploading of a new HTML file and a related file stored in the HTML file storage unit 11 and the related file storage unit 12 is received (S11), the related file to be used is specified from the description of the HTML file (S12).

  Next, the information in the file information storage unit 13 is searched for the identified related file (S13), and there is no overlap with the related file called from another HTML file, that is, the related called from another HTML file. It is confirmed whether the same related file exists in the file (S14). If the same related file exists, it is identified as a sharable related file (S15).

  Furthermore, for the specified related file, it is confirmed whether there is a related file that does not exist, that is, does not correspond to a related file that can be shared with other HTML files, and does not accept uploading from the administrator terminal 20 (S16). If there is a related file that does not exist, the administrator terminal 20 is requested to upload a related file that does not exist (S17), and it is confirmed whether the requested related file has been accepted (S18).

  If there is no related file that does not exist, or after requesting upload of a related file that does not exist and accepting upload of those related files, among the HTML file that received the upload and the related file that received the upload, Related files that do not correspond to the sharable related file are stored in the HTML file storage unit 11 and the related file storage unit 12 (S19), and information on the related file to be called from the stored HTML file is stored in the file information storage unit 13. New registration is performed (S20). According to this processing flow, a sharable related file among the related files whose upload has been accepted is discarded without being stored in the related file storage unit 12, and only information that uses the related file is stored in the file information storage unit 13. Will be registered.

  In the processing flow of FIG. 8, the administrator terminal 20 first receives an upload of a new HTML file and then uploads a necessary related file. When an upload of a new HTML file stored in the HTML file storage unit 11 is accepted (S21), a related file to be used is specified from the description of the HTML file (S22).

  Next, the information in the file information storage unit 13 is searched for the specified related file (S23), and whether there is a related file that does not exist, that is, a related file that does not correspond to a related file that can be shared with other HTML files. Confirm (S24).

  If there is no related file that does not exist, it is determined that all the related files can be shared with other HTML files. Is newly registered in the file information storage unit 13 (S26). All the related files called from the stored HTML file are shared with other HTML files.

  If there is a related file that does not exist, the administrator terminal 20 is requested to upload a related file that does not exist (S27), and it is confirmed whether the requested related file has been received (S28). When uploading of all the related files that have not been received is received, the HTML file and the related file that have been uploaded are stored in the HTML file storage unit 11 and the related file storage unit 12 (S29), and are called from the stored HTML file. Information related to the related file is newly registered in the file information storage unit 13 (S26). In this case, all or part of the related file called from the stored HTML file is not shared with other HTML files.

  FIG. 9 is a case that can occur in any of the processing flows shown in the flowcharts of FIGS. 7 and 8, but as in the example shown in FIG. 5, the HTML file “A.html” is deleted and “A “A.gif”, “C.js”, and “A.css” are called up in a state where “A.gif” and “A.css” are also deleted from the HTML file of “.html”. The HTML file “C. html” is newly uploaded.

  In this case, it is confirmed from the information stored in the file information storage unit 13 that “A.gif” and “A.css” are deleted and do not exist among the related files called from the uploaded “C.html”. Since “A.gif” and “A.css” are not uploaded together with “C.html”, it is necessary to prompt the administrator terminal 20 to upload these related files.

  FIG. 10 is a case that may occur in the processing flow shown in the flowchart of FIG. 7, but as in the example shown in FIG. 5, the HTML file “B. html” is stored in the HTML file storage unit 11 as “B. The related files of “B.gif”, “A.js”, and “B.css” called from “html” are stored in the related file storage unit 12, and “D.gif”, “A.js”, “D.css” are stored. The HTML file “D. html” that calls the related file “” is newly uploaded.

  In this case, among the related files called from the uploaded “D.html”, it is stored in the file information storage unit 13 that “A.js” is already stored in the related file storage unit 12 and can be shared. Therefore, the uploaded “A.js” is discarded without being stored in the related file storage unit 12, and “A.js” is called as a related file to be called from the “D.html” in the file information storage unit 13. By registering the use of “A.js”, it is possible to avoid that “A.js” is stored redundantly in the related file storage unit 12 and the resources of the Web server 10 are wasted. ing.

DESCRIPTION OF SYMBOLS 10 Web server 11 HTML file storage part 12 Related file storage part 13 File information storage part 14 Web page output part 15 File management part 16 File storage part 20 Administrator terminal 30 User terminal

Claims (6)

A file storage unit for storing a markup document for displaying a Web page, a related file called from the markup document, and a file storing information about the related file called from each markup document stored in the file storage unit In a Web server provided with an information storage unit, when deleting a markup document, a file erroneous deletion prevention program for preventing a related file called from another markup document from being deleted by mistake, the Web On the server,
A deletion request reception step for receiving a markup document deletion request;
A file specifying step of searching the file information storage unit for a related file to be called from a markup document that has received a deletion request in the deletion request receiving step, and specifying a related file to be called from another markup document;
A file deletion step of deleting a markup document that has received a deletion request in the deletion request reception step, and a related file to be called from the markup document excluding the related file specified in the file specification step, from the file storage unit;
As well as
An upload reception step for receiving a new markup document and an associated file to be called from the markup document;
If there is a related file that is called from the markup document that was accepted for upload in the upload acceptance step but is not included in the related file that was accepted for upload in the upload acceptance step, the related file is called from another markup document If it is not included in the related file called from another markup document by searching the file information storage unit, it is included in the related file that has been uploaded in the upload receiving step. An upload request step that requests upload of the associated file, and
A program for preventing accidental deletion of files. A file storage unit for storing a markup document for displaying a Web page, a related file called from the markup document, and a file storing information about the related file called from each markup document stored in the file storage unit In a Web server provided with an information storage unit, when deleting a markup document, a file erroneous deletion prevention program for preventing a related file called from another markup document from being deleted by mistake, the Web On the server,
A deletion request reception step for receiving a markup document deletion request;
A file specifying step of searching the file information storage unit for a related file to be called from a markup document that has received a deletion request in the deletion request receiving step, and specifying a related file to be called from another markup document;
A file deletion step of deleting a markup document that has received a deletion request in the deletion request reception step, and a related file to be called from the markup document excluding the related file specified in the file specification step, from the file storage unit;
As well as
An upload reception step for receiving a new markup document and an associated file to be called from the markup document;
For the related file called from the markup document accepted for upload in the upload accepting step, the file information storage unit is searched for whether it is included in the related file called from another markup document. A second file specifying step of specifying a related file included in the related file called from:
Of the markup document accepted in the upload acceptance step and the related file accepted in the upload acceptance step, the related file called from the other markup document identified in the second file identification step A new file storage step of storing the related files to be excluded in the file storage unit;
A program for preventing accidental deletion of files. A file storage unit for storing a markup document for displaying a Web page, a related file called from the markup document, and a file storing information about the related file called from each markup document stored in the file storage unit In a Web server provided with an information storage unit, when deleting a markup document, a file erroneous deletion prevention program for preventing a related file called from another markup document from being deleted by mistake, the Web On the server,
A deletion request reception step for receiving a markup document deletion request;
A file specifying step of searching the file information storage unit for a related file to be called from a markup document that has received a deletion request in the deletion request receiving step, and specifying a related file to be called from another markup document;
A file deletion step of deleting a markup document that has received a deletion request in the deletion request reception step, and a related file to be called from the markup document excluding the related file specified in the file specification step, from the file storage unit;
As well as
An upload acceptance step for accepting upload of a new markup document;
For the related file called from the markup document accepted for upload in the upload accepting step, the file information storage unit is searched for whether it is included in the related file called from another markup document. An upload request step for requesting an upload of a related file that is not included in the related file called by
A program for preventing accidental deletion of files. A web server having a file erroneous deletion prevention function that prevents a related file called from another markup document from being deleted by mistake when deleting a markup document,
A file storage means for storing a markup document for displaying a web page and a related file called from the markup document;
File information storage means for storing information about related files to be called from each markup document stored in the file storage means;
A deletion request receiving means for receiving a markup document deletion request;
A file specifying unit that searches the file information storage unit for a related file to be called from a markup document for which the deletion request receiving unit has received a deletion request, and specifies a related file to be called from another markup document;
A markup document for which the delete request receiving means has received a delete request, and a file delete means for deleting from the file storage means a related file called from the markup document excluding the related file specified by the file specifying means;
An upload reception means for receiving a new markup document and an associated file to be called from the markup document;
If there is a related file that is not included in the related file that has been uploaded by the upload receiving means but is received from the markup document that has received the upload, the related file that is called from another markup document If it is not included in the related file called from other markup documents by searching the file information storage means, it is included in the related file accepted by the upload receiving means. An upload request means for requesting upload of a related file that is not
A Web server provided with a function for preventing erroneous file deletion. A web server having a file erroneous deletion prevention function that prevents a related file called from another markup document from being deleted by mistake when deleting a markup document,
A file storage means for storing a markup document for displaying a web page and a related file called from the markup document;
File information storage means for storing information about related files to be called from each markup document stored in the file storage means;
A deletion request receiving means for receiving a markup document deletion request;
A file specifying unit that searches the file information storage unit for a related file to be called from a markup document for which the deletion request receiving unit has received a deletion request, and specifies a related file to be called from another markup document;
A markup document for which the delete request receiving means has received a delete request, and a file delete means for deleting from the file storage means a related file called from the markup document excluding the related file specified by the file specifying means;
An upload reception means for receiving a new markup document and an associated file to be called from the markup document;
The related information called from the markup document accepted by the upload accepting unit is not included in the related file called from another markup document, and the file information storage unit is searched to find another markup document. A second file specifying means for specifying a related file included in the related file called from:
Of the markup document accepted by the upload accepting unit and the related file accepted by the upload accepting unit, a related file called from another markup document identified by the second file identifying unit New file storage means for storing related files to be excluded in the file storage means;
A Web server provided with a function for preventing erroneous file deletion. A web server having a file erroneous deletion prevention function that prevents a related file called from another markup document from being deleted by mistake when deleting a markup document,
A file storage means for storing a markup document for displaying a web page and a related file called from the markup document;
File information storage means for storing information about related files to be called from each markup document stored in the file storage means;
A deletion request receiving means for receiving a markup document deletion request;
A file specifying unit that searches the file information storage unit for a related file to be called from a markup document for which the deletion request receiving unit has received a deletion request, and specifies a related file to be called from another markup document;
A markup document for which the delete request receiving means has received a delete request, and a file delete means for deleting from the file storage means a related file called from the markup document excluding the related file specified by the file specifying means;
An upload acceptance means for accepting upload of a new markup document;
The related information called from the markup document accepted by the upload accepting unit is not included in the related file called from another markup document, and the file information storage unit is searched to find another markup document. An upload request means for requesting upload of a related file that is not included in the related file called from,
A Web server provided with a function for preventing erroneous file deletion.