CN109446445B

Movatterモバイル変換

Info

Publication number: CN109446445B
Application number: CN201811238199.6A
Authority: CN
Inventors: 张志亮
Original assignee: Beijing Lewo Wuxian Technology Co ltd
Current assignee: Beijing happy I unlimited Technology Co., Ltd.
Priority date: 2018-10-23
Filing date: 2018-10-23
Publication date: 2022-03-22
Anticipated expiration: 2038-10-23
Also published as: CN109446445A

Abstract

The embodiment of the application provides a resource acquisition method and a resource acquisition device, which relate to the technical field of computers, and the method comprises the following steps: when detecting that the currently stored first domain name is an invalid domain name, generating a second domain name based on a preset domain name generation rule; sending the second domain name to each client; when a resource request which is sent by a client and carries a target resource identifier is received, a target path corresponding to the target resource identifier is obtained; and sending the target path to the client. When a second domain name sent by a preset server is received, storing the second domain name; receiving a target path sent by the server; splicing the second domain name and the target path to obtain a second URL of the target resource; and acquiring the target resource through the second URL. By the method and the device, time for obtaining the target resource can be saved, and user experience is improved.

Description

Resource acquisition method and device

Technical Field

The present application relates to the field of computer technologies, and in particular, to a resource obtaining method and apparatus.

Background

When a user uses a client, the user needs to obtain a certain resource, and at this time, the client sends a resource request corresponding to the resource to a server in communication connection with the client. Resources in the internet include various files such as texts, pictures, audio, video and the like.

The server stores a URL (Uniform Resource Locator) corresponding to a large number of resources, where the URL includes a domain name and a path. After receiving the resource request, the server determines the URL of the resource (i.e., the target resource) corresponding to the resource request, and then directly sends the URL of the target resource to the client. After receiving the URL of the target resource, the client determines a resource server storing the target resource according to the domain name contained in the URL; and then, acquiring the target resource in the resource server according to the path contained in the URL. Thereby, the user obtains the target resource. In the server, the domain names included in the URLs of the multiple resources may be the same or different.

For the same domain name, the server stores a plurality of URLs including the domain name, and when a domain name becomes an invalid domain name (for example, the domain name is added to a black list by an operator), the server needs to generate a valid domain name, determine locally stored URLs including the invalid domain name, and then modify the domain name in the URLs into the valid domain name. However, since the number of URLs is usually large and modification takes a long time, if the server receives a resource request in the modification process, the server may send the URL containing an unmodified invalid domain name to the client, so that the client cannot acquire the target resource.

Disclosure of Invention

Content of application

An object of the embodiments of the present application is to provide a method and an apparatus for acquiring a resource, which can prevent a large number of URLs including an invalid domain name from being replaced when a certain domain name becomes the invalid domain name, and can save time for acquiring a target resource and improve user experience. The specific technical scheme is as follows:

in a first aspect, a resource obtaining method is provided, where the method is applied to a server, and the method includes:

when detecting that the currently stored first domain name is an invalid domain name, generating a second domain name based on a preset domain name generation rule;

sending the second domain name to each client;

when a resource request which is sent by a client and carries a target resource identifier is received, a target path corresponding to the target resource identifier is obtained;

and sending the target path to the client.

Optionally, the method further includes:

acquiring a first Uniform Resource Locator (URL) to be stored, and determining a first index corresponding to the first URL;

respectively extracting a first domain name and a first path contained in the first URL from the first URL;

correspondingly storing the first domain name and the first index to obtain the corresponding relation between the index and the domain name;

and correspondingly storing the first path and the first index to obtain the corresponding relation between the index and the path.

Optionally, after generating the second domain name based on the preset domain name generation rule, the method further includes:

and modifying the first domain name into the second domain name in the corresponding relation between the index and the domain name.

Optionally, the obtaining of the target path corresponding to the target resource identifier includes:

determining a second index corresponding to the target resource identifier according to a pre-stored corresponding relationship between the resource identifier and the index;

and determining a target path corresponding to the second index based on the corresponding relation between the pre-stored index and the path.

Optionally, the sending the target path to the client includes:

determining a second domain name corresponding to the second index based on a corresponding relation between the pre-stored index and the domain name;

and sending the identifier of the second domain name and the target path to the client.

Optionally, the method further includes:

receiving an invalid domain name notification, wherein the invalid domain name notification carries an invalid domain name identifier;

and determining the first domain name corresponding to the invalid domain name identifier as an invalid domain name.

Optionally, the method further includes:

receiving a domain name query request sent by a client, wherein the domain name query request carries an identifier of the first domain name;

and if the identifier of the first domain name is found in a pre-stored domain name blacklist, determining the first domain name as an invalid domain name.

In a second aspect, a resource obtaining method is provided, where the method is applied to a client, and the method includes:

when a second domain name sent by a preset server is received, storing the second domain name;

when a selection instruction corresponding to a target resource is detected, sending a resource request to the server, wherein the resource request carries a target resource identifier of the requested target resource;

receiving a target path sent by the server;

splicing the second domain name and the target path to obtain a second URL of the target resource;

and acquiring the target resource through the second URL.

Optionally, before the splicing the second domain name and the target path to obtain the second URL of the target resource, the method further includes:

receiving an identifier of a second domain name sent by the server;

and acquiring the second domain name from the prestored domain names according to the identifier of the second domain name.

Optionally, the method further includes:

when receiving an invalid notification of a target resource, acquiring an identifier of a second domain name contained in the second URL;

and generating an invalid domain name notification or a domain name query request according to the identifier of the second domain name.

In a third aspect, a resource obtaining apparatus is provided, where the apparatus is applied to a server, and the apparatus includes:

the first generation module is used for generating a second domain name based on a preset domain name generation rule when the first domain name stored currently is detected to be an invalid domain name;

the first sending module is used for sending the second domain name to each client;

the first acquisition module is used for acquiring a target path corresponding to a target resource identifier when receiving a resource request which is sent by a client and carries the target resource identifier;

and the second sending module is used for sending the target path to the client.

Optionally, the apparatus further comprises:

the second acquisition module is used for acquiring a first Uniform Resource Locator (URL) to be stored and determining a first index corresponding to the first URL;

the extracting module is used for respectively extracting a first domain name and a first path contained in the first URL from the first URL;

the first storage module is used for correspondingly storing the first domain name and the first index to obtain the corresponding relation between the index and the domain name;

and the second storage module is used for correspondingly storing the first path and the first index to obtain the corresponding relation between the index and the path.

Optionally, the apparatus further comprises:

and the modifying module is used for modifying the first domain name into the second domain name in the corresponding relation between the index and the domain name.

Optionally, the first obtaining module includes:

the first determining submodule is used for determining a second index corresponding to the target resource identifier according to the corresponding relation between the pre-stored resource identifier and the index;

and the second determining submodule is used for determining a target path corresponding to the second index based on the corresponding relation between the pre-stored index and the path.

Optionally, the first sending module includes:

a third determining submodule, configured to determine, based on a correspondence between a pre-stored index and a domain name, a second domain name corresponding to the second index;

and the sending submodule is used for sending the identifier of the second domain name and the target path to the client.

Optionally, the apparatus further comprises:

the first receiving module is used for receiving an invalid domain name notification, and the invalid domain name notification carries an invalid domain name identifier;

and the first determining module is used for determining the first domain name corresponding to the invalid domain name identifier as an invalid domain name.

Optionally, the apparatus further comprises:

a second receiving module, configured to receive a domain name query request sent by a client, where the domain name query request carries an identifier of the first domain name;

and the second determining module is used for determining the first domain name as an invalid domain name when the identifier of the first domain name is found in a pre-stored domain name blacklist.

In a fourth aspect, a resource obtaining apparatus is provided, where the apparatus is applied to a client, and the apparatus includes:

the third receiving module is used for storing a second domain name sent by a preset server when the second domain name is received;

a third sending module, configured to send a resource request to the server when a selection instruction corresponding to a target resource is detected, where the resource request carries a target resource identifier of the requested target resource;

a fourth receiving module, configured to receive the target path sent by the server;

the splicing module is used for splicing the second domain name and the target path to obtain a second URL of the target resource;

and the third acquisition module is used for acquiring the target resource through the second URL.

Optionally, the apparatus further comprises:

a fifth receiving module, configured to receive an identifier of the second domain name sent by the server;

and the fourth acquisition module is used for acquiring the second domain name from the prestored domain names according to the identifier of the second domain name.

Optionally, the apparatus further comprises:

a fifth obtaining module, configured to obtain, when receiving an invalid notification of a target resource, an identifier of a second domain name included in the second URL;

and the second generation module is used for generating an invalid domain name notification or a domain name query request according to the identifier of the second domain name.

In a fifth aspect, a server is provided, which includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of the first aspect when executing the program stored in the memory.

In a sixth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when being executed by a processor, carries out the method steps of the first aspect.

In a seventh aspect, a client is provided, which includes a processor, a communication interface, a memory and a communication bus, where the processor and the communication interface complete communication between the processor and the communication interface, and the memory completes communication between the processor and the communication interface through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of the second aspect when executing the program stored in the memory.

In an eighth aspect, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the method steps of the second aspect.

According to the resource acquisition method and device provided by the embodiment of the application, the server side can generate a second domain name based on a preset domain name generation rule when detecting that a currently stored first domain name is an invalid domain name, and then send the second domain name to each client side; and after receiving the second domain name, each client stores the second domain name. The server side can acquire a target path corresponding to the target resource identifier and send the target path to the client side when receiving the resource request which is sent by the client side and carries the target resource identifier; and the client splices the second domain name and the target path to obtain a second URL of the target resource, and then acquires the target resource through the second URL. According to the scheme, when the currently stored first domain name is the invalid domain name, the second domain name is generated and sent to each client, so that the client can obtain the valid second domain name, the second domain name and the received target path are spliced to obtain the second URL, the target resource can be obtained based on the second URL, the situation that a large number of URLs containing the invalid domain name are replaced is avoided, the time for obtaining the target resource can be saved, and the user experience is improved.

Of course, not all advantages described above need to be achieved at the same time in the practice of any one product or method of the present application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a flowchart of a method for resource acquisition according to an embodiment of the present application;

fig. 2 is a flowchart of a method for resource acquisition according to an embodiment of the present application;

fig. 3 is a flowchart of a method for resource acquisition according to an embodiment of the present application;

fig. 4 is a flowchart of a method for resource acquisition according to an embodiment of the present application;

fig. 5 is a flowchart of a method for resource acquisition according to an embodiment of the present application;

fig. 6 is a flowchart of an example of a resource obtaining method according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a resource acquisition apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a resource acquisition apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a client according to an embodiment of the present application.

Detailed Description

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 only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides a resource acquisition method, which is applied to a server, wherein the server can be a background service system of an application program, the background service system can comprise a server, a super server, a cluster system, a middle-range system, a mainframe and other devices which provide resources for a client, and the client can be a personal computer, a mobile phone and other electronic devices. In the embodiment of the application, the resources required to be acquired by the user are all stored in the preset resource server, and the resources are not stored in the server. The server can provide resources to the client through the resource obtaining method provided by the embodiment of the application when receiving the resource request sent by the client.

For convenience of understanding, the embodiment of the present application first describes a storage process of a URL, and as shown in fig. 1, the embodiment of the present application provides a method for storing a URL, where the specific processing process is as follows:

step 101, obtaining a first URL to be stored, and determining a first index corresponding to the first URL.

In implementation, a large number of URLs can be stored in advance in the server, the server can acquire the first URLs to be stored one by one after receiving a preset batch storage instruction, and the server can also take a certain new URL as the first URL to be stored when receiving the new URL.

After obtaining the first URL to be stored, the server may generate an index (i.e., a first index) according to a preset index generation rule, and use the first index as an index corresponding to the first URL. In addition, the server side can also obtain the resource identifier of the resource corresponding to the first URL, and correspondingly store the resource identifier of the resource corresponding to the first URL and the first index, so as to establish the corresponding relationship between the first index and the resource identifier.

Step 102, respectively extracting a first domain name and a first path contained in the first URL from the first URL.

In implementation, a URL configuration rule may be preset in the server, and after the server obtains the first URL, the server may analyze the first URL according to the preset URL configuration rule to determine a domain name and a path included in the first URL, so as to obtain the first domain name and the first path.

For example, the first URL to be stored ishttp://www.baidu1.com/resource/test.pngThe server side can analyze the first URL according to a preset URL composition rule and determine that the domain name contained in the first URL ishttp://www.baidu1.comPng, the first URL contains a path of/resource/test.

Step 103, correspondingly storing the first domain name and the first index to obtain a corresponding relationship between the index and the domain name, so that the server determines the first domain name corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relationship between the index and the domain name.

In implementation, the server may store the first domain name and the first index correspondingly to establish a corresponding relationship between the first domain name and the first index, so as to obtain a corresponding relationship between the index and the domain name.

For example, the server generates a first index S1 according to a preset index generation rule, and then correspondingly stores the first domain namehttp://www.baidu1.comAnd a first index S1, establishing a corresponding relationship between the first domain name and the first index.

And 104, correspondingly storing the first path and the first index to obtain a corresponding relation between the index and the path, so that the server determines the first path corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the index and the path.

In implementation, for each first URL, the server may store the first path and the first index in a corresponding manner to establish a corresponding relationship between the first index and the first path, so as to obtain a corresponding relationship between the index and the path.

For example, the server side correspondingly stores the first path/resource/test.png and the first index S1, and establishes a corresponding relationship between the first index and the first path.

In the embodiment of the application, for each first URL, the server stores the first index, the first domain name, and the first path corresponding to the first URL based on the correspondence between the index and the domain name and the correspondence between the index and the path, thereby implementing storage of the first URL. By adopting the URL storage mode, the server can conveniently manage the stored URL, for example, when a certain domain name becomes an invalid domain name, the server only needs to modify the invalid domain name into an effective domain name in the corresponding relation between the index and the domain name, and does not need to modify each URL containing the invalid domain name, thereby saving a large amount of time for modifying the URL containing the invalid domain name, further enabling a user to timely obtain target resources and improving user experience.

As shown in fig. 2, based on the above proposed method for storing a URL, a processing flow of a resource obtaining method provided by the present application is described below, where the method is applied to a server, and a specific processing procedure is as follows:

step 201, when it is detected that the currently stored first domain name is an invalid domain name, generating a second domain name based on a preset domain name generation rule.

In implementation, a domain name generation rule may be preset in the server, and the server may generate a new effective domain name based on the domain name generation rule. In addition, the server side can change the preset domain name generation rule according to the received modification instruction.

When the server detects that the currently stored first domain name is an invalid domain name, an effective domain name can be generated based on a preset domain name generation rule, and the effective domain name is used as a second domain name.

For example, the first domain name currently stored by the server is http:// www.baidu1.com, when the server detects that the first domain name is an invalid domain name, the server may generate an effective domain name http:// www.baidu2.com based on a preset domain name generation rule, and http:// www.baidu2.com is a second domain name.

In the embodiment of the present application, the manner of detecting whether the first domain name is the invalid domain name by the server is various, and a detailed description will be given later in a specific process.

In a possible implementation manner, the server stores the URL by using the method shown in fig. 1, and after the server generates the second domain name based on the preset domain name generation rule, the server further performs the following steps: and in the corresponding relation between the index and the domain name, modifying the first domain name into a second domain name.

In implementation, the server may determine a first index corresponding to the first domain name in a correspondence between the index and the domain name, delete the first domain name, and store the second domain name as the domain name corresponding to the first index.

In the embodiment of the application, when the first domain name becomes the invalid domain name, the server only needs to modify the domain name corresponding to the first index from the invalid domain name to the valid domain name in the corresponding relationship between the index and the domain name, and does not need to modify each URL containing the invalid domain name. For example, when the first domain namehttp://www.baidu1.comWhen the domain name is changed into an invalid domain name, the server only needs to generate the valid domain namehttp://www.baidu2.comThen, the domain name corresponding to the first index is modified intohttp://www.baidu2.comThere is no need to modify each URL containing the first domain name one by one. Therefore, a large amount of time required for modifying the URL containing the invalid domain name can be saved, so that the user can obtain the target resource in time, and the user experience is improved.

Step 202, sending the second domain name to each client.

In implementation, the server maintains a communication connection with the plurality of clients, and the communication connection includes a bluetooth connection, a WiFi (Wireless Fidelity) connection, and a cable connection or a Wireless network connection. The server may send the second domain name to each client communicatively connected to the server.

Step 203, when receiving a resource request carrying a target resource identifier sent by a client, obtaining a target path corresponding to the target resource identifier.

In implementation, when the server receives a resource request sent by the client, the server may obtain a target resource identifier carried by the resource request, and then determine a target path corresponding to the target resource identifier. For example, the target path may be/resource/test.

The way for the server to obtain the target path corresponding to the target resource identifier is various, and the detailed process will be described in detail later.

And step 204, sending the target path to the client, so that the client performs splicing processing on the second domain name and the target path to obtain a second URL of the target resource.

In the embodiment of the application, when the first domain name becomes the invalid domain name, the server does not need to modify a plurality of locally stored URLs containing the first domain name, only needs to generate the second domain name based on the preset domain name generation rule, and sends the second domain name to each client. Therefore, when the server side responds to the resource request of the client side, only the target path corresponding to the resource request needs to be sent to the client side, so that the client side can splice the target path and the second domain name to obtain the second URL of the target resource, and the target resource is obtained according to the second URL.

Therefore, the URL containing the invalid domain name does not need to be modified one by one, the processing time is reduced, the user can obtain the target resource in time, and the user experience is improved.

In the embodiment of the present application, the manner in which the server obtains the target path corresponding to the target resource identifier is various, and the embodiment of the present application provides a feasible processing manner:

step one, according to the corresponding relation between the pre-stored resource identification and the index, determining a second index corresponding to the target resource identification.

In implementation, the server may search a resource identifier that is the same as the target resource identifier in a pre-stored correspondence between the resource identifier and the index, and use the index corresponding to the resource identifier as an index corresponding to the target resource identifier, that is, a second index.

And step two, determining a target path corresponding to the second index based on the corresponding relation between the pre-stored index and the path.

In implementation, the server may further store a corresponding relationship between the index and the path in advance, and after determining the second index, the server may search for an index that is the same as the second index in the corresponding relationship between the index and the path, and use the path corresponding to the index as the path corresponding to the second index, that is, the target path.

In the embodiment of the application, the server determines a second index corresponding to the target resource identifier according to the corresponding relationship between the pre-stored resource identifier and the index, and determines a target path corresponding to the second index according to the corresponding relationship between the pre-stored index and the path. By adopting the processing mode, the server can conveniently acquire the target path based on the resource identification, and the searching efficiency is higher.

Optionally, after the server obtains the target path corresponding to the target resource identifier, for different numbers of domain names stored in the server and the client, processing manners when the server sends the target path to the client are also different, and the following two cases are specifically included:

in the first case, when the number of domain names stored in the server and the client is one, the server directly sends the target path to the client.

In case two, when the number of domain names stored in the server and the client is multiple, the server executes the following steps:

step 1, determining a second domain name corresponding to a second index based on a pre-stored corresponding relationship between the index and the domain name.

In implementation, the server may pre-store a corresponding relationship between the index and the domain name, and after determining the second index, the server may search for an index that is the same as the second index in the corresponding relationship between the index and the domain name, and use the domain name corresponding to the index as the domain name corresponding to the second index, that is, the second domain name.

And step 2, sending the identifier of the second domain name and the target path to the client.

In implementation, the server side obtains the identifier of the second domain name, and sends the identifier of the second domain name and the target path to the client side.

In the embodiment of the application, when the number of the domain names stored in the server and the client is multiple, the server determines a second domain name corresponding to a second index based on a pre-stored corresponding relationship between the index and the domain name, and then sends the identifier of the second domain name and the target path to the client together. Therefore, the client can determine the second domain name corresponding to the target path from the plurality of locally stored domain names, and the problem that the client cannot acquire the target resource due to the fact that the target path is spliced with other domain names to obtain wrong URLs is avoided.

In the embodiment of the present application, the manner of detecting whether the first domain name is an invalid domain name by the server is various, and the embodiment of the present application provides two feasible processing manners:

as shown in fig. 3, the processing procedure of the first mode is as follows:

step 301, receiving an invalid domain name notification.

And the invalid domain name notification carries an invalid domain name identifier. In a feasible implementation manner, an operator may issue an invalid domain name announcement, the invalid domain name announcement includes an invalid domain name, a technician may input the invalid domain name included in the invalid domain name announcement into a management device, and the management device may generate an invalid domain name notification and send the invalid domain name notification to a server. The server may store an invalid domain name identifier corresponding to the invalid domain name in a locally stored domain name blacklist.

In implementation, when receiving the invalid domain name notification, the server may obtain the invalid domain name identifier carried by the invalid domain name notification.

Step 302, determining the first domain name corresponding to the invalid domain name identifier as an invalid domain name.

In implementation, the server locally queries a first domain name having the same identifier as the invalid domain name identifier, and takes the first domain name as the invalid domain name.

In the embodiment of the application, the server acquires the invalid domain name identifier carried by the invalid domain name notification by receiving the invalid domain name notification, and determines the first domain name corresponding to the invalid domain name identifier as the invalid domain name. The server side can effectively detect the existence of the invalid domain name by adopting the processing mode so as to timely modify the invalid domain name into the valid domain name, further enable a user to timely acquire the target resource and improve the user experience.

As shown in fig. 4, the processing procedure of the second mode is as follows:

step 401, receiving a domain name query request sent by a client.

The domain name query request carries an identifier of the first domain name.

In implementation, the server may receive a domain name query request sent by the client, and obtain an identifier of the first domain name carried in the domain name query request.

Step 402, if the identifier of the first domain name is found in the pre-stored domain name blacklist, determining the first domain name as an invalid domain name.

In implementation, after acquiring the identifier of the first domain name, the server may search the identifier of the first domain name in a domain name blacklist stored in advance, and if an invalid domain name identifier identical to the identifier of the first domain name is found, determine that the first domain name is an invalid domain name; and if the invalid domain name identifier which is the same as the identifier of the first domain name is not found, determining that the first domain name is a valid domain name.

In the embodiment of the application, the server acquires the identifier of the first domain name carried in the domain name query request by receiving the domain name query request sent by the client, and determines the first domain name as an invalid domain name if the identifier of the first domain name is found in the domain name blacklist. The server side can effectively detect the existence of the invalid domain name by adopting the processing mode so as to timely modify the invalid domain name into the valid domain name, further enable a user to timely acquire the target resource and improve the user experience.

As shown in fig. 5, the present application further provides a resource obtaining method, where the method is applied to a client, and the specific processing procedure is as follows:

step 501, when a second domain name sent by a preset server is received, storing the second domain name.

In implementation, the client may store a domain name file in advance, where the domain name file includes a domain name locally stored by the client, and the domain name locally stored by the client may be one or multiple. The client may store the second domain name into the domain name file when receiving the second domain name sent by the server.

Step 502, when a selection instruction corresponding to a target resource is detected, a resource request is sent to a server.

The resource request may carry a target resource identifier of a requested target resource. The client may store a resource identifier file in advance, and the resource identifier file may include resource identifiers of a plurality of resources.

In implementation, when a user needs to acquire a certain resource, the user may select an icon corresponding to the resource at the client, and the client may receive a selection instruction corresponding to the resource, take the resource corresponding to the selection instruction as a target resource, and then acquire a resource identifier of the target resource stored in advance.

The client can generate a resource request based on the target resource identifier of the target resource and send the resource request to a server communicatively connected to the client.

Step 503, receiving the target path sent by the server.

And step 504, splicing the second domain name and the target path to obtain a second URL of the target resource.

In implementation, the client may splice the second domain name and the received target path according to a preset URL configuration rule to obtain a URL, that is, the second URL of the target resource.

For example, the client constructs the second domain name according to the URL construction rule of the preceding path and the following path of the domain namehttp://www.baidu2.comAnd the URL is obtained by splicing with the target path/resource/testhttp://www.baidu2.com/resource/test.pngI.e. the second URL of the target resource.

And 505, acquiring the target resource through the second URL.

In implementation, the client determines the resource server storing the target resource through the second domain name included in the second URL, then determines the storage location of the target resource in the resource server through the target path included in the second URL, and then the client acquires the target resource from the resource server.

In the embodiment of the application, when the first domain name becomes the invalid domain name, the client receives and stores the second domain name sent by the server. In this way, after the client detects the selection instruction corresponding to the target resource and sends the resource request to the server, the client only needs to receive the target path sent by the server and splice the second domain name and the target path to obtain the second URL of the target resource, so that the target resource is obtained through the second URL. Therefore, when the first domain name becomes the invalid domain name, the client can directly acquire the target resource based on the second URL containing the second domain name, the condition that the target resource cannot be acquired based on the URL containing the invalid domain name sent by the server in the prior art is avoided, the time for acquiring the target resource can be saved, and the user experience is improved.

Optionally, after the client receives the target path sent by the server, the processing manner for determining the second domain name by the client is also different according to the difference of the number of the domain names stored in the server and the client, and the specific two cases are as follows:

in the first case, when the number of the domain names stored in the server and the client is one, the client uses the domain name as a second domain name, and splices the second domain name and the target path.

In case two, for the case that the number of domain names stored in the server and the client is multiple, before the client splices the second domain name and the target path to obtain the second URL of the target resource, the following steps are further executed:

step 1, receiving the identifier of the second domain name sent by the server.

In implementation, the client may receive the identifier of the second domain name sent by the server while receiving the target path sent by the server.

And 2, acquiring the second domain name from the prestored domain names according to the identifier of the second domain name.

In implementation, the client may determine, from a plurality of domain names included in the domain name file stored in advance, that the domain name corresponding to the identifier of the second domain name is the second domain name.

In the embodiment of the application, the client receives the identifier of the second domain name sent by the server, and acquires the second domain name from the pre-stored domain names, so that the situation that the client cannot acquire the target resource due to the fact that the target path is spliced with other domain names to obtain wrong URLs is avoided.

Optionally, the client may send an invalid domain name notification or a domain name query request to the server, so that the server detects whether the first domain name is an invalid domain name. The embodiment of the present application further provides an implementation manner for generating an invalid domain name notification or a domain name query request, and the specific processing flow is as follows:

step one, when the client receives the invalid notification of the target resource, the identifier of the second domain name contained in the second URL is obtained.

In implementation, when the client cannot acquire the target resource from the preset resource server through the second URL, the preset resource server may send an invalid notification to the client, and after receiving the invalid notification, the client may acquire the identifier of the second domain name included in the second URL.

And step two, generating an invalid domain name notification or a domain name query request according to the identifier of the second domain name.

In implementation, the client may use the identifier of the second domain name as an invalid domain name identifier, and generate an invalid domain name notification based on the invalid domain name identifier, where the invalid domain name notification carries the identifier of the second domain name. The client side can send the invalid domain name notification to the server side in real time, and the client side can also send the invalid domain name notification generated in the current sending period to the server side together according to the preset sending period.

The client may also use the identifier of the second domain name as an invalid domain name identifier, and generate a domain name query request based on the invalid domain name identifier, where the domain name query request carries the identifier of the second domain name. The client side can send the domain name query request to the server side in real time, and the client side can also send the domain name query request to the server side when sending the resource request.

In the embodiment of the application, when the client receives the invalid notification of the target resource, the client acquires the identifier of the second domain name included in the second URL, and generates the invalid domain name notification or the domain name query request according to the identifier of the second domain name. Therefore, the client can determine whether the invalid domain name exists according to the target resource acquisition result in real time, and timely feed back the condition of the invalid domain name to the server, so that the server can timely modify the invalid domain name into the valid domain name, a user can timely acquire the target resource, and user experience is improved.

As shown in fig. 6, the present application further provides an example of a resource obtaining method, where the specific processing procedure is as follows:

step 601, when the server detects that the currently stored first domain name is an invalid domain name, generating a second domain name based on a preset domain name generation rule.

In practice, the specific processing procedure of this step is the same as that ofstep 201.

Step 602, the server sends the second domain name to each client.

In practice, the specific processing procedure of this step is the same as that ofstep 202.

Step 603, when the client receives a second domain name sent by a preset server, storing the second domain name.

In practice, the specific processing procedure of this step is the same as that ofstep 501.

Step 604, when the client detects the selection instruction corresponding to the target resource, the client sends a resource request to the server.

In practice, the specific processing procedure of this step is the same as that ofstep 502.

Step 605, when the server receives the resource request carrying the target resource identifier sent by the client, obtain a target path corresponding to the target resource identifier.

In practice, the specific processing procedure of this step is the same as that ofstep 203.

And 606, the server sends the target path to the client, so that the client performs splicing processing on the second domain name and the target path to obtain a second URL of the target resource.

In practice, the specific processing procedure of this step is the same as that ofstep 204.

Instep 607, the client receives the target path sent by the server.

In practice, the specific processing procedure of this step is the same as that ofstep 503.

Step 608, the client performs splicing processing on the second domain name and the target path to obtain a second URL of the target resource.

In practice, the specific processing procedure of this step is the same as that ofstep 504.

And step 609, the client acquires the target resource through the second URL.

In practice, the specific processing procedure of this step is the same as that ofstep 505.

An embodiment of the present application provides a resource obtaining apparatus, where the apparatus is applied to a server, and as shown in fig. 7, the apparatus includes:

afirst generating module 710, configured to generate a second domain name based on a preset domain name generating rule when it is detected that the currently stored first domain name is an invalid domain name;

afirst sending module 720, configured to send the second domain name to each client;

a first obtainingmodule 730, configured to obtain a target path corresponding to a target resource identifier when receiving a resource request that is sent by a client and carries the target resource identifier;

asecond sending module 740, configured to send the target path to the client.

Optionally, the apparatus further comprises:

Optionally, the first obtaining module includes:

Optionally, the first sending module includes:

Optionally, the apparatus further comprises:

An embodiment of the present application further provides a resource obtaining apparatus, where the apparatus is applied to a client, and as shown in fig. 8, the apparatus includes:

athird receiving module 810, configured to store a second domain name sent by a preset server when the second domain name is received;

athird sending module 820, configured to send a resource request to the server when a selection instruction corresponding to a target resource is detected, where the resource request carries a target resource identifier of the requested target resource;

afourth receiving module 830, configured to receive the target path sent by the server;

asplicing module 840, configured to splice the second domain name and the target path to obtain a second URL of the target resource;

a third obtainingmodule 850, configured to obtain the target resource through the second URL.

Optionally, the apparatus further comprises:

The embodiment of the present application further provides a server, as shown in fig. 9, which includes aprocessor 901, acommunication interface 902, amemory 903, and acommunication bus 904, where theprocessor 901, thecommunication interface 902, and thememory 903 complete mutual communication through thecommunication bus 904,

amemory 903 for storing computer programs;

theprocessor 901 is configured to implement the following steps when executing the program stored in the memory 903:

sending the second domain name to each client;

and sending the target path to the client.

Optionally, the method further includes:

Optionally, the sending the target path to the client includes:

Optionally, the method further includes:

The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

The communication interface is used for communication between the electronic equipment and other equipment.

The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

The embodiment of the present application further provides a client, as shown in fig. 10, which includes aprocessor 1001, acommunication interface 1002, amemory 1003 and acommunication bus 1004, wherein theprocessor 1001, thecommunication interface 1002 and thememory 1003 complete mutual communication through thecommunication bus 1004,

amemory 1003 for storing a computer program;

theprocessor 1001 is configured to implement the following steps when executing the program stored in the memory 1003:

receiving a target path sent by the server;

and acquiring the target resource through the second URL.

receiving an identifier of a second domain name sent by the server;

Optionally, the method further includes:

In yet another embodiment provided by the present application, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of any of the above-mentioned methods for resource acquisition.

In yet another embodiment provided by the present application, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method for resource acquisition as described in any of the above embodiments.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A resource acquisition method is applied to a server side and comprises the following steps:

acquiring a first URL to be stored, and determining a first index corresponding to the first URL;

correspondingly storing the first domain name and the first index to obtain a corresponding relation between the index and the domain name, so that the server determines the first domain name corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the index and the domain name;

correspondingly storing the first path and the first index to obtain a corresponding relation between the indexes and the paths, so that the server determines a first path corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the indexes and the paths;

sending the second domain name to each client;

and sending the target path to the client, so that the client splices the second domain name and the target path to obtain a second Uniform Resource Locator (URL) of the target resource.

2. The method according to claim 1, wherein after generating the second domain name based on the preset domain name generation rule, the method further comprises:

3. The method of claim 1, wherein the obtaining the target path corresponding to the target resource identifier comprises:

4. The method of claim 3, wherein sending the target path to the client comprises:

5. The method of claim 1, further comprising:

6. The method of claim 1, further comprising:

7. A resource acquisition method is applied to a client, and comprises the following steps:

when a second domain name sent by a preset server is received, storing the second domain name, wherein the second domain name is generated by the server, and the generation mode of the second domain name is as follows: the server side obtains a first URL to be stored, and determines a first index corresponding to the first URL; respectively extracting a first domain name and a first path contained in the first URL from the first URL; correspondingly storing the first domain name and the first index to obtain a corresponding relation between the index and the domain name, so that the server determines the first domain name corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the index and the domain name; correspondingly storing the first path and the first index to obtain a corresponding relation between the indexes and the paths, so that the server determines a first path corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the indexes and the paths; when detecting that the currently stored first domain name is an invalid domain name, generating a second domain name based on a preset domain name generation rule;

receiving a target path sent by the server;

and acquiring the target resource through the second URL.

8. The method according to claim 7, wherein before the splicing the second domain name and the target path to obtain the second URL of the target resource, the method further includes:

receiving an identifier of a second domain name sent by the server;

9. The method of claim 7, further comprising:

10. A resource acquisition device, wherein the device is applied to a server, and the device comprises:

the second storage module is used for correspondingly storing the first path and the first index to obtain the corresponding relation between the index and the path;

11. The apparatus of claim 10, further comprising:

12. The apparatus of claim 10, wherein the first obtaining module comprises:

13. The apparatus of claim 12, wherein the first sending module comprises:

14. The apparatus of claim 10, further comprising:

15. The apparatus of claim 10, further comprising:

16. A resource acquisition device, applied to a client, the device comprising:

a third receiving module, configured to store a second domain name sent by a preset server when the second domain name is received, where the second domain name is: the server side obtains a first URL to be stored, and determines a first index corresponding to the first URL; respectively extracting a first domain name and a first path contained in the first URL from the first URL; correspondingly storing the first domain name and the first index to obtain a corresponding relation between the index and the domain name, so that the server determines the first domain name corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the index and the domain name; correspondingly storing the first path and the first index to obtain a corresponding relation between the indexes and the paths, so that the server determines a first path corresponding to the first index according to the first index corresponding to the resource identifier of the resource request to be responded and the corresponding relation between the indexes and the paths; when the first domain name stored currently is detected to be an invalid domain name, generating a second domain name based on a preset domain name generation rule;

17. The apparatus of claim 16, further comprising:

18. The apparatus of claim 16, further comprising:

19. The server is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication among the processors and the memory through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of any of claims 1-6 when executing a program stored in the memory.

20. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of claims 1 to 6.

21. The client is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the memory through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of any of claims 7 to 9 when executing a program stored in the memory.

22. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any of the claims 7-9.