CN112565358A

CN112565358A - File uploading method, device, equipment and storage medium

Info

Publication number: CN112565358A
Application number: CN202011341104.0A
Authority: CN
Inventors: 李春祝
Original assignee: Wuhan United Imaging Healthcare Co Ltd
Current assignee: Wuhan United Imaging Healthcare Co Ltd
Priority date: 2020-11-25
Filing date: 2020-11-25
Publication date: 2021-03-26
Anticipated expiration: 2040-11-25
Also published as: CN112565358B

Abstract

The application relates to a file uploading method, a file uploading device, computer equipment and a storage medium, wherein after a transfer server receives a file uploading request sent by a client, based on a pre-configured uploading server list, health check is carried out on each uploading server in the uploading server list according to a preset rule, the first uploading server passing the health check is determined as a target uploading server, and then server information of the target uploading server is sent to the client so as to indicate the client to upload a target file to the target uploading server; the method can improve the reliability of file uploading.

Description

File uploading method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for uploading a file.

Background

Along with the informatization process, the status of information resources is more and more widely agreed, and electronic documents are used as the most important resource form of electronic government affairs, the proportion is increased day by day, the value is more and more fully determined, and the importance of document management work is gradually highlighted.

In the process of file management, a general enterprise uploads files to a server for management, and particularly important files are stored in a specified server for management; however, in the process of uploading a file to a server, various problems often occur, for example, the file server cannot upload the file because the disk space reaches the upper limit, the access of the file server is not safe, the uploaded file has security, and the like, which all cause serious influence on the uploading of the file, so that the management reliability of the existing file is low.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a file uploading method, device, apparatus and storage medium capable of improving file uploading reliability.

In a first aspect, an embodiment of the present application provides a method for uploading a file, where the method includes:

a transfer server receives a file uploading request sent by a client; the file uploading request is used for requesting to upload a target file;

the transfer server carries out health check on each uploading server in the uploading server list according to a preset rule based on a pre-configured uploading server list, and determines the first uploading server passing the health check as a target uploading server;

the transfer server sends server information of a target uploading server to the client; the server information is used for indicating the client to upload the target file to the target uploading server.

In one embodiment, the file upload request includes health standard information of the server; the health check is used for detecting whether each uploading server meets health standard information.

In one embodiment, the health standard information is generated according to at least one of the size of the file, the type of the file and the importance of the file.

In one embodiment, the above-mentioned transit server performs health check on each upload server in the upload server list based on a preconfigured upload server list, and determines a first upload server that passes the health check as a target upload server, including:

the transfer server acquires the uploading server positioned at the head in the uploading server list from the uploading server list, and performs health check on the server information of the acquired first uploading server;

if the health check of the first uploading server passes, the transfer server determines the first uploading server as a target uploading server;

if the health check of the first uploading server fails, deleting the first uploading server from the first of the uploading server list by the transfer server, adding the deleted first uploading server to the tail end of the uploading server list, then continuously taking a new first uploading server which is newly positioned at the first in the uploading server list, and carrying out health check on the new first uploading server;

and the transfer server always takes the uploading server positioned at the head in the uploading server list until the target uploading server is determined.

In one embodiment, the file uploading request carries permission verification information of a target file;

before the transit server performs health check on each uploading server in the uploading server list and determines the first uploading server passing the health check as the target uploading server, the method further includes:

the transfer server verifies the uploading authority of the target file according to the authority verification information;

if the uploading authority passes the verification, the transfer server executes health check on each uploading server in the uploading server list, and determines the first uploading server passing the health check as a target uploading server;

if the uploading authority check is not passed, the transfer server returns error information to the client; the error information is used for indicating that the target file has no uploading authority.

In one embodiment, the permission verification information includes at least one of an application identifier of an application program of the target file, an authentication token of the target file, and a file name of the target file;

the application identifier is used for verifying whether the target file is a file of a specified application program;

the identity authentication token is used for verifying whether the identity of the target file is legal or not;

and the file name is used for verifying whether the target file name carries sensitive information.

In one embodiment, the verifying the uploading permission of the target file by the transit server according to the permission verification information includes:

the transfer server determines the authority level of the application program to which the target file belongs; different authority levels correspond to different authority verification information;

and the transfer server verifies the uploading authority of the target file according to the verification information corresponding to the authority level of the application program to which the target file belongs.

In one embodiment, the health check includes: at least one of port and IP connection state, memory state, hard disk resource, CPU resource state, server type and server grade.

In one embodiment, the method further comprises:

after receiving a file uploading request sent by a client, a transfer server confirms whether a Uniform Resource Identifier (URI) and a request type of the file uploading request are legal or not;

if the file uploading request is legal, the transfer server analyzes the file uploading request; if the request is illegal, the transfer server returns request error information to the client.

In a second aspect, an embodiment of the present application provides a server, including:

the receiving module is used for receiving a file uploading request sent by a client; the file uploading request is used for requesting to upload a target file;

the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for carrying out health check on each uploading server in an uploading server list according to a preset rule based on a pre-configured uploading server list and determining the first uploading server passing the health check as a target uploading server;

the sending module is used for sending the server information of the target uploading server to the client; the server information is used for indicating the client to upload the target file to the target uploading server.

In a third aspect, an embodiment of the present application provides a computer device, including a memory and a processor, where the memory stores a computer program, and the processor implements the steps of any one of the methods provided in the foregoing embodiments of the first aspect when executing the computer program.

In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of any one of the methods provided in the embodiments of the first aspect.

According to the file uploading method, the file uploading device, the computer equipment and the storage medium, after a transfer server receives a file uploading request sent by a client, based on a pre-configured uploading server list, health check is carried out on each uploading server in the uploading server list according to a preset rule, the first uploading server passing the health check is determined as a target uploading server, and then server information of the target uploading server is sent to the client so as to indicate the client to upload a target file to the target uploading server; according to the method, when the target file needs to be uploaded, after the transfer server receives an uploading request of the target file, the target uploading server which meets the health check is determined from the uploading server list, so that the stable uploading server is returned through the health check, the access safety of the file uploading service is ensured, and the file uploading reliability is improved; in addition, health detection is sequentially carried out on the uploading servers in the uploading server list, the first found health server is determined as the target uploading server, other uploading servers do not need to be checked, operation resources are saved, and file uploading efficiency is improved.

Drawings

FIG. 1 is a diagram illustrating an application environment of a method for uploading files according to an embodiment;

fig. 1a is an internal structure diagram of a client/relay server/upload server according to an embodiment;

fig. 2 is a flowchart illustrating a method for uploading a file according to an embodiment;

FIG. 2a is a diagram illustrating a client-server interaction according to an embodiment;

fig. 3 is a schematic flowchart of a file uploading method according to another embodiment;

fig. 4 is a schematic flowchart of a file uploading method according to another embodiment;

fig. 5 is a flowchart illustrating a method for uploading files according to another embodiment;

fig. 6 is a schematic flowchart of a file uploading method according to another embodiment;

FIG. 7 is a flowchart of a method for uploading a file, according to an embodiment;

fig. 8 is a block diagram illustrating an exemplary file uploading apparatus;

FIG. 9 is a block diagram of a computer device internal, according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The method for uploading the file provided by the present application can be applied to an application environment shown in fig. 1, and includes a client, a transfer server, and an upload server, where the client includes, but is not limited to, a personal computer, a notebook computer, a smart phone, a tablet computer, a portable wearable device, and the like, and the embodiment of the present application does not limit this. The transit server and the uploading server include but are not limited to a general server and a special server, and are not limited to a desktop server, a rack server, a cabinet server, a blade server and the like; the transit server may be a Domain Name System (DNS) server. Further, the internal structure diagrams of the client, the transit server and the upload server can all refer to the internal structure diagram shown in fig. 1a, and the processor in fig. 1a is used for providing computing and control capability. The memory comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database is used for storing relevant data in the file uploading process. The network interface is used for communicating with other external devices through network connection. The computer program is executed by a processor to implement a method of file upload.

The general process of uploading files to the server is as follows: the method comprises the steps that a client uploads a file to a designated server, after the file is successfully uploaded, data synchronization is achieved through an rsync + inotify mechanism, specifically, the requirement for data backup with low real-time requirements can be met through the rsync mechanism, the data of a file server is periodically backed up to another download server, data mirroring is conducted on a local disk periodically, and the like; various changes of a file system can be monitored through an inotify mechanism, and rsync synchronization is triggered when any file changes, so that the problem of real-time performance of synchronous data is solved. When the client downloads the file, the uploading server plays a role of downloading the server, and the client downloads the file. Therefore, the server side synchronizes the data of the master file server and the slave file server in real time. However, in the process of uploading a file to a server, various problems often occur, including but not limited to untimely file synchronization during file uploading, inability to upload due to the fact that the disk space of a file server reaches an upper limit, insecure file access, and the like. The following describes in detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by embodiments and with reference to the drawings. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that in the method for uploading a file provided by the present application, the execution main body in fig. 2 to fig. 7 is a server (relay server), where the execution main body may also be a device for uploading a file, where the device may be implemented as part or all of the server by software, hardware, or a combination of software and hardware.

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments.

In an embodiment, fig. 2 provides a method for uploading a file, where the embodiment relates to a specific process in which a relay server finds a target upload server from a preconfigured upload server list according to a file upload request of a client, and instructs the client to upload a file to the target upload server, and as shown in fig. 2, the embodiment includes the following steps:

s101, a transfer server receives a file uploading request sent by a client; the file uploading request is used for requesting to upload the target file.

The relay server refers to a server which is responsible for an access service for uploading files between the client and the upload server, and may be a DNS server or other servers meeting the requirements. The transit server may perform parallel expansion according to actual requirements, for example, every 500 concurrent times of requests of a single file DNS server increase, 1 DNS needs to be added for balancing, and for example, the transit server may be separately deployed in a nginnx port mapping manner. The client is a client for uploading the user operation file, the client provides a visual interface, and the user can perform related operation of file uploading in the visual interface. For example, when a file needs to be uploaded, the user triggers a file upload button on a visual interface of the client, and then a file upload request can be sent from the client to the transfer server.

In practical application, after sending a file uploading request to a transfer server, the transfer server determines that a file is required to be uploaded at a current client, so that the file uploading request can be only a request signal and does not carry a target file to be uploaded; however, the file uploading request itself is to request to upload a file, so that when the file uploading request is sent, the target file to be uploaded can also be carried and sent to the transfer server together.

The target file to be uploaded includes, but is not limited to, medical image data generated by magnetic resonance, Computed Tomography (CT), ultrasound, various X-ray machines, various infrared instruments, microscopy, and the like, and may be files, data, and the like generated in other industry fields.

And S102, the transfer server performs health check on each uploading server in the uploading server list according to a preset rule based on a pre-configured uploading server list, and determines the first uploading server passing the health check as a target uploading server.

After the transfer server receives the file uploading request, a target uploading server which can be uploaded needs to be determined in a pre-configured uploading server list according to the target file to be uploaded currently. The uploading server list is a list generated by uploading servers capable of supporting uploading files in advance and then stored in the transfer server, that is, a plurality of uploading server list information (domain names and ports) can be configured in the configuration file of the transfer server in advance, and the uploading server list can be continuously expanded and added with new uploading servers or delete unavailable uploading servers in the using process. For example, for every 100 times of the number of concurrent uploads of a single file, one uploading server for uploading (downloading) is added, and a standby machine is added for parallel expansion, so that the uploading server can be flexibly expanded in parallel by updating the uploading server list.

However, it should be noted that the upload server capable of supporting the uploaded file only indicates that the upload server is supportable in the dimension of the service authority and does not indicate that the upload server has the ability to receive the uploaded target file, for example, the upload server a belongs to the target file configured in the upload server list and having the authority to receive the uploaded target file, but cannot store the complete target file due to its internal memory or cannot normally receive the target file due to the damaged transmission interface, in this case, the client uploads the target file to the upload server a, which may cause the unreliable access and storage of the target file. Therefore, the transit server needs to determine a target upload server from the upload server list.

Specifically, the process of the transit server determining the target upload server may be: and performing health check on each uploading server in the uploading server list according to a preset rule, and determining the first uploading server passing the health check as a target uploading server. The preset rule may be a rule that the relay server performs health check on each upload server in the upload server list, and the rule may include a rule of detecting an order, for example, an order from top to bottom of the list, or an order from a few times to a large number of times that the relay server is determined as a target upload server within a preset time period, and the like; in one embodiment, the file upload request sent by the client to the relay server further includes key information of the client and/or the upload file, and the preset rule may be adjusted according to the key information. That is, after the transfer server receives the file uploading request sent by the client, the preset rule can be adaptively adjusted according to the information carried in the file uploading request, and health check can be performed on each uploading server in the uploading server list according to the adjusted preset rule; for example, the key information is information such as the security level, priority level or type of the file, then the relay server adjusts the preset rule to be a rule with stability from high to low, that is, according to the security level of the file, the uploading server performs health check according to the rule with stability from high to low, so that the uploading server with higher stability is selected to store the file with higher security level, and the security of the file is improved. Or if the file type is medical images, the uploading server sequentially performs health check according to rules supporting medical image storage, and the like.

Taking the order from top to bottom according to the list as an example, the relay server performs health check on each uploading server pair one by one according to the order, and optionally, the content of performing health check includes: at least one of port and IP connection state, memory state, hard disk resource, CPU resource state, server type and server grade.

Detecting whether the connection state of the port and the IP is normal, for example, calling the current state of the port through a port command, and judging whether the current state is a closed state or an open state, wherein if the current state is the closed state, the open state represents a normal state, namely a healthy state, and if the current state is the closed state, the open state is abnormal; the memory state, the hard disk resource state and the CPU resource state are detected, mainly detecting the remaining memory or resource, for example, if the current resource of the CPU resource state is 98%, it indicates that the CPU has no redundant resource to upload the target file, and the corresponding upload server is in an unhealthy state. The detection server type mainly refers to different types of uploading servers, for example, a medical image data server, an equipment management data server and the like, and different types of target files can be uploaded according to different types of uploading servers; the server levels are mainly different levels divided by the uploading server, for example, the uploading server with higher importance level is used for storing more private important files such as medical reports; and relatively speaking, some videos are more focused on the need of facing remote film reading, and then the videos can be stored in a cloud PACS server with a relatively low importance level. Therefore, when the uploading server is subjected to health check, the server type and the level of the uploading server can be detected together, so that the determined target uploading server is ensured to be safer and more reliable.

Optionally, the file uploading request includes health standard information of the server; the health check is used for detecting whether each uploading server meets health standard information. Optionally, the health standard information is generated according to at least one of the size of the file, the type of the file, and the importance of the file.

That is, the file upload request sent by the client may carry the health standard information of the server, which may be based on the size of the file, the type of the file, and the weight of the fileAt least one item of importance is generated, so that the transit server can check the health according to the healthSign boardAnd carrying out health check on each uploading server in the uploading server list by the standard information.

For example, the user may be prompted on the visual interface of the client to input the requirement of the uploading server to be uploaded of the target file to be uploaded, and the requirement is the health standard information. Specifically, the available memory, available CPU, etc. of the server to be uploaded can be determined by combining the size of the target file, the degree of confidentiality, the type of the file, and the importance of the file, and what type of server to be uploaded is determined, and what level the importance level belongs to.

Taking the size of the target file as 30M, the type as a medical report, the importance as a private file, and the like as examples, the client determines the health standard information as follows according to the information of the target file: the available internal memory of the server and the available CPU support the file size of 30M, belong to a medical image data server, and have very high importance level, and after the transfer server receives the file uploading request and obtains the health standard information, the transfer server detects each uploading server in the uploading server list one by one, and determines the server which is healthy and accords with the health standard information as the target uploading server, thus, the health standard information required by the client and the health content defined by the transfer server can be combined, the files with different characteristics can be stored in the servers which accord with different requirements, and the safety and reliability of the determined target uploading server can be further ensured.

In addition, when the transfer server performs health check on each uploading server one by one, once an uploading server meeting requirements (healthy or healthy and meeting health standard information) is determined, the uploading server is determined as a target uploading server without executing downwards, and only the first determined uploading server meeting the requirements is determined as the target uploading server, so that the efficiency of the target uploading server is improved, and resource waste is avoided.

After the health check is performed on each uploading server in the uploading server list one by one, the transfer server may maintain the uploading server in the uploading server list according to the detection result, for example, delete the unhealthy uploading server, or mark the unhealthy uploading server, or send the unhealthy uploading server to the maintenance module for maintenance, and the like. The upgradeability and reliability of the uploading servers in the uploading server list can be ensured through maintenance operation. Further, the transfer server may store historical upload server information corresponding to each type of health standard information, and when a next upload request is received, the transfer server modifies the upload server list according to the historical upload server information corresponding to the currently received health standard information. Furthermore, the transfer server can return the historical uploading server information corresponding to the currently received health standard information to the client, when the client sends an uploading request next time, the client can directly send the uploading server information to the transfer server through the historical uploading server information, and the designated transfer server directly checks the information of the uploading server, so that the efficiency of determining the target uploading server is improved.

S103, the transfer server sends the server information of the target uploading server to the client; the server information is used for indicating the client to upload the target file to the target uploading server.

After the transfer server determines the target uploading server, the server information of the target uploading server needs to be sent to the client so as to instruct the client to accurately and quickly upload the target file to the target uploading server according to the server information. The server information includes, but is not limited to, an upload server IP, a port, a file unique identifier, an interface type, and the like, that is, the upload server IP, the port, and the interface type may indicate the correctness of accessing the target upload server by the client, and the file unique identifier may indicate the client to prompt the user to name the name of the target file according to the file unique identifier, so as to meet the requirement of receiving the file by the target upload server.

Certainly, for the client, the client can directly access the target file to the target uploading server according to the server information, and upload the target file to the target uploading server for storage; or the client sends the target file to the transfer server again to instruct the transfer server to transmit the target file to the target uploading server; in any target file transmission mode, the client can store the server information of the target uploading server and is associated with the target file, so that the storage path of the target file can be conveniently and quickly located in the client when the target file is inquired subsequently.

Taking the example that the transit server is a DNS server, the communication between the DNS server and the client is described: as shown in figure 2a, with reference to figure,

the DNS server adopts a Netty framework as a server side, is always started and waits for the connection of the client side. For example, the http protocol version number of the DNS server is 1.1, only post requests are supported, and the like; the DNS server communicates with the client using Netty. The DNS server monitors the running state of each uploading server device, and after receiving a file uploading request of a client, health check is carried out on each uploading server to determine a healthy target uploading server. After the DNS server determines a healthy target uploading server, the server information such as IP, port, file unique identification, interface type and the like of the healthy target uploading server is returned to the client. Finally, the DNS server can release the resource and close the HTTP connection.

In the method for uploading a file provided by this embodiment, after receiving a file uploading request sent by a client, a transfer server performs health check on each uploading server in an uploading server list according to a preset rule based on a preconfigured uploading server list, determines a first uploading server passing the health check as a target uploading server, and then sends server information of the target uploading server to the client to instruct the client to upload a target file to the target uploading server; according to the method, when the target file needs to be uploaded, after the transfer server receives an uploading request of the target file, the target uploading server which meets the health check is determined from the uploading server list, so that the stable uploading server is returned through the health check, the access safety of the file uploading service is ensured, and the file uploading reliability is improved; in addition, health detection is sequentially carried out on the uploading servers in the uploading server list, the first found health server is determined as the target uploading server, other uploading servers do not need to be checked, operation resources are saved, and file uploading efficiency is improved.

On the basis of the above embodiment, the following provides an embodiment in which the transit server determines the target upload server, and as shown in fig. 3, the embodiment includes:

s201, the transfer server acquires the uploading server positioned at the head in the uploading server list from the uploading server list, and performs health check on the server information of the acquired first uploading server.

In this embodiment, the preset rule is a rule in which the order from top to bottom in the upload server list is used as a detection order, and the transfer server first obtains the upload server located at the head from the upload server list, and performs health check on the server information of the obtained head upload server.

For example, the upload server list is shown in table 1 below, where table 1 only shows the upload server id in the upload server list, and other information in the upload server list is not shown. The transit server retrieves upload server N1 located at the head in table 1 and performs a health check on upload server N1.

TABLE 1

The content and the mode of the health check performed by the transfer server on the upload server may refer to the content in the above embodiments, and are not described herein again.

And S202, if the health check of the first uploading server passes, the transfer server determines the first uploading server as a target uploading server.

When the first uploading server is subjected to health check, two conditions exist in the check result: one is that the health check is passed and one is that the health check is not passed. For the condition that the health check of the first uploading server passes, the transfer server can directly determine the first uploading server as the target uploading server. For example, if the upload server N1 health check passes in table 1, then upload server N1 is determined to be the target upload server.

It can be understood that, when the relay server performs the health check, the health check may include not only the content of the health check performed by the relay server in the above embodiment, but also the requirement of the health standard information carried in the file upload request sent by the client for checking, and if the content of the health check of the relay server and the health standard information exist at the same time, it is necessary that both the content of the health check of the relay server and the health standard information are both in compliance to determine that the health check of the first upload server passes. The health check performed by any one of the uploading servers is the same as that performed in the above case, and will not be described again.

And S203, if the health check of the first uploading server fails, deleting the first uploading server from the first of the uploading server list by the transfer server, adding the deleted first uploading server to the tail end of the uploading server list, continuing to fetch a new first uploading server which is newly positioned at the first in the uploading server list, and carrying out health check on the new first uploading server.

For the case that the health check of the first uploading server fails, the transfer server needs to continue checking the next uploading server, specifically, the transfer server may delete the first uploading server from the first of the uploading server list, add the first uploading server to the last of the uploading server list, then continue to fetch a new first uploading server located at the first in the uploading server list, and perform health check on the new first uploading server.

For example, if the health check of the upload server N1 in table 1 fails, the upload server N1 is deleted from the top of the upload server list and added to the end of the upload server list, the order of the upload servers in table 1 changes to the order shown in table 2, and in table 2, the new top upload server located at the top is the upload server N2, that is, the relay server continues to perform the health check on the upload server N2.

TABLE 2

Upload server N2
	Upload server N3
Upload server N4
	Upload server N5
Upload server N1

And S204, the transfer server always takes the uploading server positioned at the head in the uploading server list until the target uploading server is determined.

When the transit server performs health check on the upload server N2, there are two cases of pass and fail in the check result, that is, different check results are executed according to the manners of S202 and S203, respectively, that is, in the process of performing polling according to the manners of S202 and S203, the transit server always takes the upload server located at the head in the upload server list to perform health check until the target upload server is determined.

It should be emphasized that, when the transit server starts the health check from the first position initially in the upload server list, the first health check fails, the transit server is placed at the last position in the list, and the health check is continued on the new first upload server.

In the embodiment, the health examination is placed at the tail end of the list, and in the examination process, the transfer server only needs to fetch the uploading server which is positioned at the head in the uploading server list all the time until the target uploading server is determined, so that the health examination of the uploading server in the list is conveniently and quickly completed.

In an embodiment, a new upload server may be added to perform parallel expansion on the upload servers, and after the new upload server is added, the transit server needs to update the upload server list, the updated upload server list is shown in table 3 below, and M1 and M2 in table 3 are newly added upload servers, as shown in table 3, the newly added upload server may be at the last of the existing upload servers, i.e., at the last of the upload server list, or may be added at an intermediate position of the existing upload servers, i.e., at an intermediate position in the upload server list, so that by adding the new upload server, a new task is allocated to the newly added upload server, so that the task workload of the existing upload servers can be balanced, and low-load high-performance operation of each upload server is ensured.

TABLE 3

Upload server N1
	Upload server N2
Upload server N3
	Upload server M1
Upload server N4
	Upload server N5
Upload server M2

In order to further improve the security and reliability of file uploading, different uploading permissions may be set for the file, and as shown in fig. 4, an embodiment is provided to explain the uploading permission of the verification target file. This embodiment comprises the steps of:

s301, the transfer server checks the uploading authority of the target file according to the authority verification information.

The present embodiment may be performed before the transit server performs a health check on each upload server in the upload server list and determines the first upload server that passes the health check as the target upload server.

The authority verification information can be carried in the file uploading request or can be pre-configured in a transfer server; taking the example carried in the file uploading request, after receiving the file uploading request, the transfer server analyzes the authority verification information of the target file carried in the file uploading request, and verifies the uploading authority of the target file by using the authority verification information.

Optionally, the permission verification information includes at least one of an application identifier of an application program to which the target file belongs, an authentication token of the target file, and a file name of the target file; the application identifier is used for verifying whether the target file is a file of a specified application program; the identity authentication token is used for verifying whether the identity of the target file is legal or not; and the file name is used for verifying whether the target file name carries sensitive information.

In practical application, respective corresponding application identifiers and identity authentication tokens can be configured according to different applications in an enterprise, correct application identifiers need to be verified when files are uploaded, namely whether target files are files of specified application programs or not is verified, and if not, the uploading permission of the target files is verified to be not passed and uploading is not allowed; and checking the correct identity authentication token, namely checking whether the identity of the target file is legal or not, matching the identity authentication token carried in the target file with a pre-stored identity authentication token, if the matching is successful, indicating that the identity authentication is legal, and if the identity authentication is passed, uploading the identity authentication token, otherwise, not allowing the identity authentication token to be uploaded; the file name can be verified, that is, whether sensitive information is carried in the target file name is verified, or whether the target file is in a blacklist is verified by taking the file name, the application identifier and the identity authentication token as a basis, and if yes, uploading is not allowed.

Optionally, as shown in fig. 5, an implementation manner of the transit server checking the uploading permission of the target file according to the permission verification information includes the following steps:

s401, the transfer server determines the authority level of the application program to which the target file belongs; different permission levels correspond to different permission verification information.

The implementation manner is based on that permission levels are divided for application programs of uploaded files, and different permission levels correspond to different permission verification information, for example, permission levels of application programs include: level 0, level 1, level 2 (the levels become higher in order); wherein, level 0 indicates that no authority is needed and the file is directly accessed, and the application program with the authority level of 0 can be uploaded without limitation and verification; level 1 indicates that a Single Sign On (SSO) token is required to allow uploading, and the method is mainly applicable to BS applications, wherein the SSO is used in an environment where multiple systems coexist, and a user does not need to log in other systems after logging in one place, that is, one-time logging of the user can obtain trust of all other systems; level 2 indicates that a user ID and password need to be provided to allow uploading, mainly applicable to CS applications.

After the transfer server receives the target file, the authority level of the application program to which the target file belongs is determined. Specifically, the transfer server may query the permission level of the application program to which the target file belongs in the permission level record table according to the identifier of the application program, and may also issue an instruction to the client, where the instruction requests the client to provide the permission level of the application program to which the target file belongs and a certification file of the permission level.

In practical application, three external calling interfaces can be provided at the client, the three external calling interfaces respectively correspond to the 0/1/2 three permission levels, namely, the client uploads the target file through the corresponding external calling interface, and thus, after receiving the target file, the transfer server can determine the permission level of the target file according to the calling interface. The embodiment of the present application does not limit the specific manner of determining the permission level of the application program to which the target file belongs.

S402, the transfer server checks the uploading authority of the target file according to the verification information corresponding to the authority level of the application program to which the target file belongs.

And after determining the authority level of the application program to which the target file belongs, the transfer server verifies the uploading authority of the target file according to the verification information and the verification mode corresponding to the authority level. In the implementation mode, different verification information is set according to the authority level of the application program, so that the security authentication of the target file is realized, the file is prevented from being attacked maliciously, and the access security of the transfer server is ensured.

And S302, if the uploading authority passes the verification, the transfer server executes the step of performing health check on each uploading server in the uploading server list and determining the first uploading server passing the health check as the target uploading server.

In this step, the uploading authority of the target file passes the verification in the step S201, and in this case, the transfer server performs a health check on each uploading server in the uploading server list, and determines the first uploading server that passes the health check as the target uploading server. The specific implementation process has been described in detail in the foregoing embodiments, and is not described herein again.

S303, if the uploading authority check is not passed, the transfer server returns error information to the client; the error information is used for indicating that the target file has no uploading authority.

In this step, the target file upload permission check in the step S201 is not passed, in which case, the relay server returns error information to the client, where the error information is used to indicate that the target file does not have the upload permission; for example, the manner of returning the error information may be that the client pops up the received error information to a display box on a visual interface, and a voice prompt may be configured to ensure that the user may receive the error information.

In this embodiment, the transfer server checks the uploading permission of the target file according to the permission verification information, only when the uploading permission passes the checking, the transfer server performs the steps of performing health check on each uploading server in the uploading server list and determining the target uploading server, and if the uploading permission does not pass the checking, the transfer server returns error information to the client to indicate that the target file does not have the uploading permission. Therefore, the health check step is executed only when the target file is determined to have the uploading authority, and resource waste caused by the fact that the target file does not have the uploading authority after the health check step is executed is avoided. When the uploading authority of the target file is verified, different authority verification information is adopted for authority levels of different application programs to which the target file belongs, so that verification is performed pertinently, accuracy of file uploading authority verification is improved, and safe uploading of different files is guaranteed.

In some scenarios, there is a phenomenon that the file upload request sent by the client is not legal, and in order to avoid these situations, the file upload request may be legally confirmed, and in an embodiment, as shown in fig. 6, the method further includes:

s501, after receiving a file uploading request sent by a client, the transit server judges whether the Uniform Resource Identifier (URI) and the request type of the file uploading request are legal or not.

After receiving the file upload request sent by the client, the transit server determines whether a Uniform Resource Identifier (URI) of the file upload request is valid, for example, whether a request address, an IP address, information to be requested, and the like in the URI are valid, and further, when the transit server supports only the POST request, verifies whether the request is the POST request.

S502, if the file is legal, the transfer server analyzes the file uploading request; if the request is illegal, the transfer server returns request error information to the client.

If the URI is verified to be legal, the transfer server analyzes the file uploading request, and the step of performing health check on each uploading server can be executed after the file uploading request is analyzed; however, if the transit server fails to verify, the transit server may notify the client by returning the request error message, for example, the format of the request error message may be: and after receiving the request error information, the client can modify the file uploading request and then resend the file uploading request.

In this embodiment, after receiving a file upload request sent by a client, a transfer server determines whether a uniform resource identifier URI and a request type of the file upload request are legal or not, and the transfer server parses the file upload request only when the file upload request is legal, and if the file upload request is illegal, the transfer server returns request error information to the client, so that resource waste caused by the fact that the file upload request is illegal is found after the transfer server parses the file upload request is avoided, and the security and reliability of file upload are improved by validity confirmation.

In addition, in an embodiment, the present application further provides an embodiment of a file uploading method, taking the relay server as a DNS server as an example, as shown in fig. 7, the embodiment includes:

and S1, the DNS server receives the file uploading request sent by the client.

S2, the DNS server determines whether the uniform resource identifier URI and the request type of the file upload request are valid.

S3, if legal, the DNS server analyzes the file uploading request; if the request is illegal, the DNS server returns request error information to the client.

And S4, the DNS server checks the uploading authority of the target file according to the authority verification information of the target file carried in the file uploading request.

And S5, if the uploading authority passes the verification, the DNS server takes the uploading server positioned at the head in the uploading server list from the uploading server list, and performs health check on the server information of the taken first uploading server.

And S6, if the health check of the first uploading server passes, the DNS server determines the first uploading server as the target uploading server.

And S7, if the health check of the first uploading server fails, deleting the first uploading server from the first of the uploading server list by the DNS server, adding the deleted first uploading server to the tail end of the uploading server list, continuing to fetch a new first uploading server which is newly positioned at the first in the uploading server list, and carrying out health check on the new first uploading server.

And S8, the DNS server always takes the uploading server positioned at the head in the uploading server list until the target uploading server is determined.

S9, the DNS server sends the server information of the target uploading server to the client; the server information is used for indicating the client to upload the target file to the target uploading server.

S10, if the uploading authority check is not passed, the DNS server returns error information to the client; the error information is used for indicating that the target file has no uploading authority.

In the method for uploading a file provided by this embodiment, the DNS server is responsible for dynamically allocating a healthy upload server to the client by monitoring the operating state of the upload server device, and checking the security of the uploaded file to ensure the security mechanism of file access and the processes of file upload trace and the like. The implementation manner of each step in the embodiment of fig. 7 is only an example, and is not limited to this, and the order of each step may be adjusted in practical application as long as the purpose of each step can be achieved.

It should be understood that although the various steps in the flow charts of fig. 2-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-7 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.

In one embodiment, as shown in fig. 8, there is provided an apparatus for uploading a file, the apparatus including: receiving module 10, determining module 11, and sending module 12, wherein:

the receiving module 10 is configured to receive a file upload request sent by a client; the file uploading request is used for requesting to upload a target file;

the determining module 11 is configured to perform health check on each upload server in the upload server list according to a preset rule based on a preconfigured upload server list, and determine a first upload server that passes the health check as a target upload server;

a sending module 12, configured to send server information of a target upload server to a client; the server information is used for indicating the client to upload the target file to the target uploading server.

In one embodiment, the health criteria information is generated based on at least one of a size of the file, a type of the file, and an importance of the file.

In one embodiment, the determining module 11 includes:

the health check unit is used for taking the uploading server positioned at the head in the uploading server list from the uploading server list and carrying out health check on the taken server information of the first uploading server;

the target determining unit is used for determining the first uploading server as a target uploading server if the health check of the first uploading server passes;

the health check unit is further configured to delete the first upload server from the first of the upload server list and add the deleted first to the last of the upload server list if the health check of the first upload server fails, and then continue to fetch a new first upload server located at the first in the upload server list to perform health check on the new first upload server;

the target determining unit is further configured to always obtain the upload server located at the head in the upload server list until the target upload server is determined.

In one embodiment, the file uploading request carries permission verification information of the target file; the device also includes:

the verification module is used for verifying the uploading authority of the target file according to the authority verification information;

the execution module is used for executing the step of performing health check on each uploading server in the uploading server list by the transfer server if the uploading authority passes the check, and determining the first uploading server passing the health check as a target uploading server; if the uploading authority check is not passed, the transfer server returns error information to the client; the error information is used for indicating that the target file has no uploading authority.

In one embodiment, the verification module includes:

the level determining unit is used for determining the authority level of the application program to which the target file belongs; different authority levels correspond to different authority verification information;

and the verification unit is used for verifying the uploading authority of the target file according to the verification information corresponding to the authority level of the application program to which the target file belongs.

In one embodiment, the apparatus further comprises:

the legal determining module is used for determining whether the Uniform Resource Identifier (URI) and the request type of the file uploading request are legal or not after the file uploading request sent by the client is received;

the processing module is used for analyzing the file uploading request if the file uploading request is legal; and if the request is illegal, returning request error information to the client.

For specific limitations of the file uploading device, reference may be made to the above limitations of the file uploading method, which are not described herein again. The modules in the file uploading device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 9. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of file upload. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like. The processor in the computer device may also be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

Those skilled in the art will appreciate that the architecture shown in fig. 9 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:

receiving a file uploading request sent by a client; the file uploading request is used for requesting to upload a target file;

based on a pre-configured uploading server list, carrying out health check on each uploading server in the uploading server list according to a preset rule, and determining the first uploading server passing the health check as a target uploading server;

sending server information of a target uploading server to a client; the server information is used for indicating the client to upload the target file to the target uploading server.

The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:

The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), enhanced SDRA M (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method for uploading a file, the method comprising:

the transfer server sends the server information of the target uploading server to the client; the server information is used for instructing the client to upload the target file to the target uploading server.

2. The method of claim 1, wherein the file upload request includes health criteria information of a server; the health check is used for detecting whether each uploading server meets the health standard information.

3. The method of claim 2, wherein the health criteria information is generated based on at least one of a size of the file, a type of the file, and an importance of the file.

4. The method according to any one of claims 1 to 3, wherein the transit server performs a health check on each uploading server in the uploading server list according to a preconfigured uploading server list, and determines a first uploading server passing the health check as a target uploading server, including:

if the health check of the head uploading server passes, the transfer server determines the head uploading server as the target uploading server;

if the health check of the first uploading server fails, deleting the first uploading server from the first of the uploading server list by the transfer server, adding the deleted first uploading server to the tail end of the uploading server list, and then continuously taking a new first uploading server which is newly positioned at the first in the uploading server list to perform health check on the new first uploading server;

5. The method of any of claims 1-3, wherein performing the health check comprises: at least one of port and IP connection state, memory state, hard disk resource, CPU resource state, server type and server grade.

6. The method according to any one of claims 1 to 3, wherein the file uploading request carries permission verification information of the target file;

before the transit server performs health check on each uploading server in the uploading server list and determines the first uploading server passing the health check as a target uploading server, the method further includes:

7. The method according to any one of claims 1-3, further comprising:

after receiving the file uploading request sent by the client, the transfer server confirms whether a Uniform Resource Identifier (URI) and a request type of the file uploading request are legal or not;

if the file uploading request is legal, the transfer server analyzes the file uploading request; and if the request is illegal, the transfer server returns request error information to the client.

8. A server, characterized in that the server comprises:

the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for carrying out health check on each uploading server in an uploading server list according to a preset rule based on a pre-configured uploading server list, and determining the first uploading server passing the health check as a target uploading server;

the sending module is used for sending the server information of the target uploading server to the client; the server information is used for instructing the client to upload the target file to the target uploading server.

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.