CN107592373B - Information request method and device for multi-domain name page and user terminal - Google Patents
Information request method and device for multi-domain name page and user terminal Download PDFInfo
- Publication number
- CN107592373B CN107592373B CN201610543492.8A CN201610543492A CN107592373B CN 107592373 B CN107592373 B CN 107592373B CN 201610543492 A CN201610543492 A CN 201610543492A CN 107592373 B CN107592373 B CN 107592373B
- Authority
- CN
- China
- Prior art keywords
- request
- webpage
- site
- software client
- domain name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The embodiment of the invention provides an information request method and device of a multi-domain name page and a user terminal. The information request method of the multi-domain name page is applied to a software client installed on a user terminal, and comprises the following steps: receiving an information acquisition request sent by a webpage; judging whether a request authorization result of a webpage under any domain name of a site to which the webpage belongs exists in the software client; and when a request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client, allowing the webpage sending the information acquisition request to acquire information corresponding to the information acquisition request from the user terminal. By using the information request method, the information request device and the user terminal of the multi-domain name page, the same request authorization result can be used by the pages under different domain names of the same site, and the interaction convenience is improved.
Description
Technical Field
The invention relates to the technical field of application software, in particular to an information request method and device for a multi-domain name page and a user terminal.
Background
With the increasing popularity and development of handheld terminals, it is becoming a trend to access the internet using various software clients, such as browsers, installed in the handheld terminals. With the advancement of technology, the content display of web pages is also increasingly diversified. The page content can include text information, picture information, audio information, video information and the like, and interaction between the page and the user can be realized, for example, user information such as position information and address list information is acquired, and user experience is greatly improved.
Today, pages need to obtain user authorization before obtaining user information. The current mainstream practice is to store the authorization request selection result according to the domain name. This storage method has a problem if a certain site has several domain names, for example, the main domain name of a certain service website is:
www.testdomain.com
the domain names corresponding to different services are:
www.sport.testdomain.com
www.news.testdomain.com
www.ent.testdomain.com
if the pages under different domain names all need to acquire user information, the user can respectively pop up an authorization request dialog box when accessing the pages of different services, so that the interactive operation is relatively complicated, and the interactive experience of the user is reduced.
Disclosure of Invention
In view of this, embodiments of the present invention provide an information request method, an apparatus, and a user terminal for a multi-domain page, so as to solve the problem in the prior art that when information is obtained, all pages under different domains of the same site need to be authorized by a user, so that interactive operations are complicated.
The embodiment of the invention provides an information request method of a multi-domain name page, which is applied to a software client installed on a user terminal and comprises the following steps:
receiving an information acquisition request sent by a webpage;
judging whether a request authorization result of a webpage under any domain name of a site to which the webpage belongs exists in the software client; and
and when a request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client, allowing the webpage sending the information acquisition request to acquire information corresponding to the information acquisition request from the user terminal.
Preferably, the method further comprises:
when the request authorization result of the webpage under any domain name of the site to which the webpage belongs does not exist in the software client, displaying an authorization request dialog box;
when receiving an operation that a user selects to approve authorization, generating a request authorization result of a webpage sending the information acquisition request; and
storing the generated request authorization result in the software client.
Preferably, the request authorization result includes a preset keyword corresponding to the site, and the request authorization results of the web pages in different domain names of the same site include the same keyword.
Preferably, the step of determining whether a request authorization result of a web page under any domain name of a site to which the web page belongs exists in the software client includes:
inquiring by using keywords corresponding to the site, judging whether a request authorization result comprising the keywords exists in the software client, and if the request authorization result comprising the keywords exists, judging that the request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client; otherwise, judging that the request authorization result of the webpage under any domain name of the site to which the webpage belongs does not exist in the software client.
Another preferred embodiment of the present invention provides an information requesting device for a multi-domain page, which is applied to a software client installed in a user terminal, and the information requesting device for a multi-domain page includes:
the request receiving module is used for receiving an information acquisition request sent by a webpage;
the judging module is used for judging whether a request authorization result of the webpage under any domain name of the site to which the webpage belongs exists in the software client; and
and the request processing module is used for allowing the webpage sending the information acquisition request to acquire the information corresponding to the information acquisition request from the user terminal when the request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client.
Preferably, the request processing module is further configured to display an authorization request dialog box when the request authorization result of the web page in any domain name of the site to which the web page belongs does not exist in the software client, generate the request authorization result of the web page sending the information acquisition request when an operation that a user selects to approve authorization is received, and store the generated request authorization result in the software client.
Another preferred embodiment of the present invention provides a ue, including:
a memory;
a processor; and
a software client installed in the memory and an information request device of a multi-domain page applied to the software client, the information request device of the multi-domain page including one or more software function modules executed by the processor, the information request device of the multi-domain page including:
the request receiving module is used for receiving an information acquisition request sent by a webpage;
the judging module is used for judging whether a request authorization result of the webpage under any domain name of the site to which the webpage belongs exists in the software client; and
and the request processing module is used for allowing the webpage sending the information acquisition request to acquire the information corresponding to the information acquisition request from the user terminal when the request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client.
Compared with the prior art, the information request method, the information request device and the user terminal for the multi-domain name page provided by the embodiment of the invention can judge whether the request authorization result of the web page under any domain name of the site to which the web page belongs exists or not when receiving the information acquisition request sent by the web page, and can directly allow the web page sending the information acquisition request to acquire the corresponding information when the request authorization result exists. The information request scheme enables the pages under different domain names of the same site to share the request authorization result, avoids the situation that the pages under different domain names need to carry out multiple authorization request interactions, and improves the interaction convenience, thereby improving the user experience.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic diagram illustrating interaction between a user terminal and a server according to a preferred embodiment of the present invention.
Fig. 2 is a block diagram of a user terminal shown in fig. 1.
Fig. 3 is a functional block diagram of an information requesting apparatus of a multi-domain page shown in fig. 2.
Fig. 4 is a flowchart of an information requesting method for a multi-domain page according to a preferred embodiment of the present invention.
Description of the main elements
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Fig. 1 is an interaction diagram of at least one user terminal 100 and a server 200 according to a preferred embodiment of the present invention. The user terminal 100 may communicate with the server 200 through a network 300 for data communication or interaction. The server 200 may provide at least one software client 110 (shown in fig. 2) suitable for various operating systems, such as an installation package of Application programs (APPs) for downloading by the user terminal 100. After the user terminal 100 accesses the server 200 through the network 300, the software client 110 suitable for the user terminal 100 may be downloaded from the server 200 through the network 300 and installed.
In this embodiment, the server 200 may be, but is not limited to, a web site server, an ftp (file transfer protocol) server, and the like. The user terminal 100 may be, but is not limited to, a Personal Computer (PC), a tablet PC, a smart phone, a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), and the like. The network 300 may be, but is not limited to, a wired network or a wireless network. The operating system of the user terminal 100 may be, but is not limited to, an Android (Android) system, an IOS system, a Windows phone system, and the like.
As shown in fig. 2, is a block diagram of the user terminal 100 shown in fig. 1. The user terminal 100 includes a software client 110, an information requesting device 120 for a multi-domain name page, a memory 101, a storage controller 102, a processor 103, a peripheral interface 104, an input/output unit 105, an audio unit 106, a display unit 107, and a radio frequency unit 108.
The memory 101, the memory controller 102, the processor 103, the peripheral interface 104, the input/output unit 105, the audio unit 106, the display unit 107 and the radio frequency unit 108 are electrically connected to each other directly or indirectly, so as to implement data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The information requesting device 120 of the multi-domain name page comprises at least one software function module which can be stored in the memory 101 in the form of software or firmware (firmware) or solidified in the software client 110. The memory 101 stores the software client 110 downloaded and installed from the server 200 by the user terminal 100, and the information requesting device 120 for a multi-domain page is applied to the software client 110. The processor 103 is used for executing executable modules stored in the memory 101, such as software functional modules and computer programs included in the information request device 120 of the multi-domain name page.
The Memory 101 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 101 is configured to store a program, and the processor 103 executes the program after receiving the execution instruction. Access to the memory 101 by the processor 103 and possibly other components may be under the control of the memory controller 102.
The processor 103 may be an integrated circuit chip having signal processing capabilities. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP)), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The peripheral interface 104 couples various input/output devices to the processor 103 as well as to the memory 101. In some embodiments, the peripheral interface 104, the processor 103, and the memory controller 102 may be implemented in a single chip. In other examples, they may be implemented separately from the individual chips.
The input/output unit 105 is used for providing input data for a user to realize the interaction of the user with the user terminal 100. The input/output unit 105 may be, but is not limited to, a mouse, a keyboard, and the like.
The audio unit 106 provides an audio interface to the user, which may include one or more microphones, one or more speakers, and audio circuitry.
The display unit 107 provides an interactive interface (e.g., a user operation interface) between the user terminal 100 and a user or is used to display image data. In this embodiment, the display unit 107 may be a liquid crystal display or a touch display. In the case of a touch display, the display can be a capacitive touch screen or a resistive touch screen, which supports single-point and multi-point touch operations. Supporting single-point and multi-point touch operations means that the touch display can sense touch operations generated from one or more positions on the touch display, and the sensed touch operations are sent to the processor 103 for calculation and processing.
The rf unit 108 is configured to receive and transmit radio wave signals (e.g., electromagnetic waves), so as to realize interconversion between radio waves and electrical signals, thereby realizing communication between the user terminal 100 and the network 300 or other communication devices.
It is understood that the structure shown in fig. 2 is only an illustration, and the user terminal 100 may further include more or less unit components than those shown in fig. 2, or have a different configuration from that shown in fig. 2. The various unit components shown in fig. 2 may be implemented in hardware, software, or a combination thereof.
Referring to fig. 3, a functional block diagram of the information requesting device 120 applied to the multi-domain page of the software client 110 shown in fig. 2 according to the preferred embodiment of the present invention is shown. The information requesting device 120 for the multi-domain name page includes a request receiving module 121, a judging module 122 and a request processing module 123.
The request receiving module 121 is configured to receive an information obtaining request sent by a web page.
In different application scenarios, the information obtaining request received by the request receiving module 121 may be of various types, for example, the information obtaining request may be a request requiring authorization from a user, such as a geographic location obtaining request, an address book obtaining request, and a user identity obtaining request. Taking the geographic location acquisition request as an example, geographic location (Geolocation) is one of the important features of HTML5, providing functionality for determining the location of a user. This functionality is widely used in today's web applications or web applications. Such as a browser application, a mapping application, a service application, etc. These applications provide the most appropriate service to the user by acquiring the user's current location at startup. Accordingly, the request receiving module 121 receives an information obtaining request sent by the web page when the web page is opened.
The determining module 122 is configured to determine whether a request authorization result of a web page under any domain name of a site to which the web page belongs exists in the software client 110.
In this embodiment, the software client 110 stores the request authorization result of the web pages under different domain names of different sites. When the request receiving module 121 receives the information obtaining request, the determining module 122 determines whether a request authorization result of a web page under any domain name of a site to which the web page sending the request belongs exists in the software client 110.
In order to accurately and quickly judge whether the request authorization result of the web page under any domain name of the site to which the web page sending the request belongs exists in the software client 110. Alternatively, it may be preset that each site corresponds to an identifier, and the request authorization results of the web pages under different domain names of each site are stored in the software client 110 by using the identifier corresponding to the site as a keyword. For example: a uniform resource locator (url) corresponding to each site may be preset as the keyword (other embodiments may also set other identifiers as the keywords), and the request authorization result of the web page at different domain names of each site may be stored in the software client 110 as the keyword. After such setting, the determining module 122 can query the url corresponding to the website to which the webpage sending the request belongs as a keyword, and determine whether a request authorization result with the url as the keyword exists in the software client 110.
The request processing module 123 is configured to allow the web page that sends the information obtaining request to obtain information corresponding to the information obtaining request from the user terminal 100 when a request authorization result of the web page under any domain name of the site to which the web page belongs already exists in the software client 110.
Taking the example that the request authorization results of the web pages under different domain names of each site are stored in the software client 110 by taking the url corresponding to the site as a keyword, when the determining module 122 queries the url corresponding to the site to which the web page sending the request belongs as a keyword and queries the request authorization result including the url, it indicates that the web pages under different domain names of the site have been authorized. In this case, the web page transmitting the information acquisition request is considered authorized, and the web page transmitting the information acquisition request is directly allowed to acquire information corresponding to the information acquisition request from the user terminal 100.
The request processing module 123 is further configured to display an authorization request dialog box when the request authorization result of the web page in any domain name of the site to which the web page belongs does not exist in the software client 110, generate the request authorization result of the web page that sends the information acquisition request when receiving an operation that a user selects to grant authorization, and store the generated request authorization result in the software client 110.
Similarly, for example, the request authorization result of the web page under the different domain names of each site is stored in the software client 110 by taking the url corresponding to the site as a keyword, when the determining module 122 queries the url corresponding to the site to which the web page sending the request belongs as a keyword, and the query result is that the url corresponding to the site is empty, it is determined that the web page under the different domain names of the site is not authorized. In this case, authorization authentication needs to be performed on the information acquisition request sent by the web page, and after the authorization of the user is obtained, the web page sending the information acquisition request is allowed to acquire information corresponding to the information acquisition request from the user terminal 100. If the user decides to authorize, the web page that sends the information acquisition request is denied to acquire the information corresponding to the information acquisition request from the user terminal 100.
Optionally, in the embodiment of the present invention, only when the user performs an operation of authorizing, a request authorization result of the webpage sending the information acquisition request is generated, and the generated request authorization result is stored in the software client 110. When the user performs an operation of refusing to authorize, the request refusing result of the web page for sending the information acquisition request is not generated and is not stored. To ensure that the user does not affect the experience of using the web page every time after a single rejection operation.
It should be understood that, in implementation, the request rejection result may also be stored in a manner similar to the storage of the request authorization result. Correspondingly, after the request rejection result is stored, the judging module 122 can also find the request rejection result according to the keyword, and when the judging module 122 judges that the request rejection result is stored in the software client 110, it indicates that the web pages under different domain names of the existing site have been rejected. In this case, the web page that sent the information acquisition request is determined to be a rejection request, and the web page that sent the information acquisition request is directly rejected from acquiring information corresponding to the information acquisition request from the user terminal 100.
In order to make the solution of the embodiment of the present invention clearer, the following description is made.
Assume that software client 110 is a browser. The browser extends the geocation object, adding a solution named requestOrigin, which provides a string-type parameter url. And storing the request authorization result according to the url specified in the requestOrigin scheme, wherein when the url is empty or the scheme is not called, the default value is the domain name corresponding to the page.
In use, the developer invokes the solution before invoking the acquisition of the geographic location. For the web pages under different domain names of the same site, the url parameters used when the requestOrigin () is called are the same. When the requestOrigin () is called in the page, the browser acquires a parameter url, and stores the url into the current context. When getCurrentposition () is called in the page to obtain the geographic position, the browser obtains url from the current context, and whether a request authorization result exists is checked according to the url. If the request authorization result exists, the browser performs corresponding processing according to the request authorization result, and directly allows the page to acquire the geographic position from the user terminal 100. And if the authorization result does not exist, popping up an authorization request dialog box by the browser and waiting for selection of the user. After the user selects to approve the authorization, the browser saves the authorization result in the browser by using url as a storage key word. In this example scenario, a scenario, geolocation, requestorigin, is extended to the geolocation object. The web page developer sets a geographic position query source through an interface, and the browser queries the geographic position request authorization result corresponding to the value through the value set by the interface. Therefore, the same geographical position authorization request result can be used by pages of different domain names at the same site. The repeated popping-up of the authorization request caused by different domain names can be avoided, so that the interaction convenience is improved, and the user experience is better.
In order to further improve the flexibility and convenience of the scheme in use, the storage right of the request authorization result can be given to a webpage designer for presetting in implementation.
Referring to fig. 4, a flowchart of an information requesting method applied to a multi-domain page of a software client 110 according to a preferred embodiment of the present invention is shown. The method steps defined by the method related flows may be implemented by the processor 103. The specific flow shown in fig. 4 will be described in detail below.
Step S401: and receiving an information acquisition request sent by a webpage.
In different application scenarios, the received information acquisition request may be of various types, for example, the information acquisition request may be a request requiring authorization from a user, such as a geographic location acquisition request, an address book acquisition request, and a user identity acquisition request.
In this embodiment, step S401 may be executed by the request receiving module 121 in fig. 3.
Step S402: it is determined whether the request authorization result of the web page under any domain name of the site to which the web page belongs exists in the software client 110.
In this embodiment, the software client 110 stores the request authorization result of the web pages under different domain names of different sites. Upon receiving the information acquisition request, the software client 110 determines whether there is a request authorization result of a web page under any domain name of a site to which the web page sending the request belongs.
In order to accurately and quickly determine whether a request authorization result of a web page under any domain name of a site to which a web page sending a request belongs exists in the software client 110, optionally, the request authorization result is stored in the software client 110 by using a preset url corresponding to the site as a key, and request authorization results of web pages under different domain names of the same site are stored in the software client 110 by using the same url as a key. After such setting, the software client 110 can query by using the url corresponding to the site to which the webpage sending the request belongs as a keyword, and determine whether a request authorization result using the url as the keyword exists in the software client 110.
In this embodiment, step S402 may be executed by the determining module 122 in fig. 3.
When the request authorization result of the web page under any domain name of the site to which the web page belongs already exists in the software client 110, step S403 is executed.
When the request authorization result of the web page under any domain name of the site to which the web page belongs does not exist in the software client 110, step S404, step S405, and step S406 are executed.
Step S403: the web page that has transmitted the information acquisition request is allowed to acquire information corresponding to the information acquisition request from the user terminal 100.
Step S404: an authorization request dialog is displayed.
Step S405: and when receiving the operation of agreeing to authorization selected by the user, generating a request authorization result of the webpage sending the information acquisition request.
Step S406: storing the generated request authorization result in the software client 110.
In this embodiment, steps S403 to S406 may be executed by the request processing module 123 of fig. 3.
The information request method, the information request device, and the user terminal 100 for a multi-domain page provided in the embodiments of the present invention determine whether a request authorization result of a web page under any domain name of a site to which the web page belongs exists when receiving an information acquisition request sent by the web page, and directly allow the web page sending the information acquisition request to acquire corresponding information when the request authorization result exists. The information request scheme enables the pages under different domain names of the same site to share the request authorization result, avoids the situation that the pages under different domain names need to carry out multiple authorization request interactions, and improves the interaction convenience, thereby improving the user experience.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus and method embodiments described above are illustrative only, as the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention or a part thereof, which essentially contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server 200, or a network 300 device, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It should be noted that, in this document, 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.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (14)
1. An information request method of a multi-domain name page is applied to a software client installed on a user terminal, and is characterized in that the method comprises the following steps:
receiving an information acquisition request sent by a webpage;
judging whether a request authorization result of a webpage under any domain name of a site to which the webpage belongs exists in the software client; and
when a request authorization result of a webpage under any domain name of a site to which the webpage belongs already exists in the software client, allowing the webpage sending the information acquisition request to acquire information corresponding to the information acquisition request from the user terminal, and when the webpage under different domain names of the site to which the webpage belongs is not authorized, performing authorization authentication on the information acquisition request sent by the webpage.
2. The method for requesting information of a multi-domain name page as recited in claim 1, further comprising:
when the request authorization result of the webpage under any domain name of the site to which the webpage belongs does not exist in the software client, displaying an authorization request dialog box;
when receiving an operation that a user selects to approve authorization, generating a request authorization result of a webpage sending the information acquisition request; and
storing the generated request authorization result in the software client.
3. The method for requesting information on a multi-domain name page according to claim 2, wherein the request authorization result includes a preset keyword corresponding to the site, and the request authorization results of the web pages under different domain names on the same site include the same keyword.
4. The method of claim 3, wherein the keyword comprises a uniform resource locator.
5. The method for requesting information on a multi-domain name page according to claim 3 or 4, wherein the step of determining whether the request authorization result of the web page under any domain name of the site to which the web page belongs exists in the software client comprises:
inquiring by using keywords corresponding to the site, judging whether a request authorization result comprising the keywords exists in the software client, and if the request authorization result comprising the keywords exists, judging that the request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client; otherwise, judging that the request authorization result of the webpage under any domain name of the site to which the webpage belongs does not exist in the software client.
6. The method according to claim 1, wherein the information acquisition request comprises a geographic location acquisition request for requesting acquisition of a geographic location of the user terminal.
7. An information request device of a multi-domain page is applied to a software client installed on a user terminal, and is characterized in that the information request device of the multi-domain page comprises:
the request receiving module is used for receiving an information acquisition request sent by a webpage;
the judging module is used for judging whether a request authorization result of the webpage under any domain name of the site to which the webpage belongs exists in the software client; and
the request processing module is used for allowing the webpage sending the information acquisition request to acquire information corresponding to the information acquisition request from the user terminal when a request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client, and authorization authentication needs to be carried out on the information acquisition request sent by the webpage when the webpage under different domain names of the site to which the webpage belongs does not acquire authorization.
8. The apparatus as claimed in claim 7, wherein the request processing module is further configured to display an authorization request dialog box when the request authorization result of the web page under any domain name of the site to which the web page belongs does not exist in the software client, generate a request authorization result of the web page sending the information acquisition request when receiving an operation of a user selecting to grant authorization, and store the generated request authorization result in the software client.
9. The apparatus as claimed in claim 8, wherein the request authorization result includes a preset keyword corresponding to the site, and the request authorization results of the webpages under different domain names of the same site include the same keyword.
10. The apparatus as claimed in claim 9, wherein the keyword comprises a uniform resource locator.
11. The apparatus according to claim 9 or 10, wherein the determining module is configured to query a keyword corresponding to the site, determine whether a request authorization result including the keyword exists in the software client, and if the request authorization result including the keyword exists, determine that the request authorization result of the web page under any domain name of the site to which the web page belongs already exists in the software client; otherwise, judging that the request authorization result of the webpage under any domain name of the site to which the webpage belongs does not exist in the software client.
12. The apparatus as claimed in claim 7, wherein the information obtaining request comprises a geographic location obtaining request for obtaining a geographic location of the user terminal.
13. A user terminal, comprising:
a memory;
a processor; and
a software client installed in the memory and an information request device of a multi-domain page applied to the software client, the information request device of the multi-domain page including one or more software function modules executed by the processor, the information request device of the multi-domain page including:
the request receiving module is used for receiving an information acquisition request sent by a webpage;
the judging module is used for judging whether a request authorization result of the webpage under any domain name of the site to which the webpage belongs exists in the software client; and
the request processing module is used for allowing the webpage sending the information acquisition request to acquire information corresponding to the information acquisition request from the user terminal when a request authorization result of the webpage under any domain name of the site to which the webpage belongs already exists in the software client, and authorization authentication needs to be carried out on the information acquisition request sent by the webpage when the webpage under different domain names of the site to which the webpage belongs does not acquire authorization.
14. The user terminal according to claim 13, wherein the request processing module is further configured to display an authorization request dialog box when the request authorization result of the web page in any domain name of the site to which the web page belongs does not exist in the software client, generate the request authorization result of the web page that sends the information acquisition request when receiving an operation of a user selecting to grant authorization, and store the generated request authorization result in the software client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610543492.8A CN107592373B (en) | 2016-07-08 | 2016-07-08 | Information request method and device for multi-domain name page and user terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610543492.8A CN107592373B (en) | 2016-07-08 | 2016-07-08 | Information request method and device for multi-domain name page and user terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107592373A CN107592373A (en) | 2018-01-16 |
| CN107592373B true CN107592373B (en) | 2021-06-29 |
Family
ID=61046122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610543492.8A Active CN107592373B (en) | 2016-07-08 | 2016-07-08 | Information request method and device for multi-domain name page and user terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107592373B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110968356B (en) * | 2018-09-29 | 2023-09-29 | 北京金山云网络技术有限公司 | Method and device for acquiring configuration information |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051703A (en) * | 2012-12-18 | 2013-04-17 | 北京奇虎科技有限公司 | Geographical location information-based display method and geographical location information-based display device |
| CN103905502B (en) * | 2012-12-27 | 2018-02-23 | 中国移动通信集团江苏有限公司 | A kind of method and system for obtaining customer position information |
| CN104754030B (en) * | 2015-02-12 | 2017-05-10 | 腾讯科技（深圳）有限公司 | User information obtaining method and device |
-
2016
- 2016-07-08 CN CN201610543492.8A patent/CN107592373B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107592373A (en) | 2018-01-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109218368B (en) | Method, device, electronic equipment and readable medium for realizing Http reverse proxy | |
| US8943566B2 (en) | Increased security for computer userID input fields | |
| WO2018001124A1 (en) | Webpage file sending method, webpage rendering method and apparatus, and webpage rendering system | |
| CN105472694B (en) | Method, device, terminal and storage medium for accessing WiFi through scanning two-dimensional code | |
| WO2015154666A1 (en) | Method for displaying webpage fragment on desktop and system for capturing webpage fragment to desktop for display | |
| US20150271165A1 (en) | Method And Device For Uploading Data To Social Platform | |
| JP2019530089A (en) | Method and apparatus for realizing communication between web page and native application, and electronic apparatus | |
| WO2015074459A1 (en) | Method and apparatus for opening webpage, invoking client, and creating light app | |
| JP2017501517A (en) | Method, apparatus, and system for pushing an application program, and device | |
| US20180063270A1 (en) | Methods and Systems for Signing Resource Identifiers | |
| CN109600458B (en) | Website access method and device | |
| US9832322B1 (en) | Techniques to transform network resource requests to zero rated network requests | |
| US10904210B2 (en) | Dynamic bookmarking of web addresses accessed via short URL | |
| CN107592373B (en) | Information request method and device for multi-domain name page and user terminal | |
| US10440100B2 (en) | Information processing apparatus, information processing method, and non-transitory computer readable medium | |
| CN105956202A (en) | Web page display method and web page display apparatus in browser as well as terminal | |
| CN108985013B (en) | Method, device, client and server for detecting use of SWF file by third-party application program | |
| US9742760B1 (en) | System and method for improving login and registration efficiency to network-accessed data | |
| US10965781B2 (en) | Method and server for displaying access content | |
| CN107015826B (en) | Script file loading method, terminal and server | |
| CN113515710B (en) | Page information display method and device, electronic equipment and storage medium | |
| JP6059307B1 (en) | Terminal device, information transmission method, and information transmission program | |
| CN108280105B (en) | HTTP caching method and device and user terminal | |
| JP2017138689A (en) | Image processing device, image processing method, and program | |
| CN114640718A (en) | Data processing method and device based on data processing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200619 Address after: 310052 room 508, floor 5, building 4, No. 699, Wangshang Road, Changhe street, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Alibaba (China) Co.,Ltd. Address before: 510627 Guangdong city of Guangzhou province Whampoa Tianhe District Road No. 163 Xiping Yun Lu Yun Ping B radio 14 floor tower square Applicant before: GUANGZHOU UCWEB COMPUTER TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |