CN108234665A - Redirect processing method and equipment - Google Patents
Redirect processing method and equipment Download PDFInfo
- Publication number
- CN108234665A CN108234665A CN201810027229.2A CN201810027229A CN108234665A CN 108234665 A CN108234665 A CN 108234665A CN 201810027229 A CN201810027229 A CN 201810027229A CN 108234665 A CN108234665 A CN 108234665A
- Authority
- CN
- China
- Prior art keywords
- jump
- request
- flow
- local target
- detected
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 27
- 238000000034 method Methods 0.000 claims abstract description 45
- 238000012545 processing Methods 0.000 claims abstract description 34
- 238000012795 verification Methods 0.000 claims abstract description 15
- 230000008569 process Effects 0.000 claims description 27
- 230000009191 jumping Effects 0.000 claims description 22
- 230000008439 repair process Effects 0.000 claims description 15
- 238000004458 analytical method Methods 0.000 claims description 13
- 238000001514 detection method Methods 0.000 claims description 13
- 238000012544 monitoring process Methods 0.000 claims description 12
- 230000000875 corresponding effect Effects 0.000 description 25
- 238000004891 communication Methods 0.000 description 7
- 238000004590 computer program Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000010224 classification analysis Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000029087 digestion Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- 238000007429 general method Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000035939 shock Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/148—Migration or transfer of sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Debugging And Monitoring (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses one kind to redirect processing method and equipment, and method includes preposition flow, redirect procedure and readjustment flow；Preposition flow includes obtaining step, obtains jump request；Verification step verifies the legitimacy of jump request, legal then to enter redirect procedure, otherwise enters readjustment flow；Redirect procedure includes classifying step, classifies to jump request, is divided into corresponding processing thread；Analyzing step parses the call request in jump request, obtains virtual value and then redirected according to call request, otherwise enters readjustment flow；It adjusts back flow and includes detecting step, jump request is detected, local target is jumped to if local target is detected, otherwise open jump request using browser.It is unified to receive jump request, to jump request there is verification, classification and parsing etc., jump request can be screened and be classified.There is the processing being directed to, improve whole treatment effeciency.
Description
Technical Field
The invention relates to a jump processing method and equipment.
Background
With the rapid development of front-end technologies, page skipping, interaction of various front-end technologies, external hoisting of clients and the like, the development of the front-end technologies is gradually promoted. The original jump rule with complex configuration, and more complex newly-added jump and interaction modes, the prior art is gradually not suitable for the front-end large environment with high-speed development.
In the prior art, the processing is respectively carried out according to various situations. For example, the native jump native is a process, the js jump native is another process, multiple processing modes exist in parallel, and received jump requests need to be matched one by one among the processing modes through a 'trying' method until the jump can be completed.
This approach does not seem to be a nuisance in situations where there is less data to process. However, as the number of service lines increases, a plurality of jump requests need to be processed simultaneously, and the existing method reduces the processing speed, causes serious fragmentation, and is very easy to cause various downtime (or abnormal, shock) problems.
Disclosure of Invention
The invention aims to provide a jump processing method and equipment, which can uniformly acquire jump requests, gradually screen and classify the jump requests and improve the processing efficiency.
The jump processing method of the invention comprises the following steps: a pre-flow, a skip flow and a callback flow; wherein, the pre-flow comprises: an obtaining step, obtaining a jump request; a verification step, namely verifying the legality of the jump request, if the request is legal, entering a jump flow, and otherwise, entering a callback flow; the skipping process comprises the following steps: classifying, namely classifying the jump requests and dividing the jump requests into corresponding processing threads; analyzing, namely analyzing a calling request in the jumping request, jumping according to the calling request if an effective value is obtained, and entering the callback flow if the effective value is not obtained; the callback process comprises the following steps: and a detection step, namely detecting the jump request, jumping to a local target if the local target is detected, and otherwise opening the jump request by using a browser.
The jump processing method as described above, wherein the verifying step includes: and at least verifying whether the jump request has a jump type, a jump destination and parameters corresponding to the call request, and if the jump request has the parameters, determining that the jump request is legal.
The jump processing method as described above, wherein the jump request at least includes a type parameter and a json parameter, and the type parameter is mapped with the corresponding jump type and the jump destination; and the json parameter is mapped with the corresponding calling request.
In the foregoing jump processing method, in the analyzing step, the json parameter is analyzed, if an effective value is obtained, a jump is performed according to the effective value, and if the effective value is not obtained, the callback process is entered.
The jump processing method as described above, wherein the local target at least includes: any one of a local application, local cache data, and a local service request.
The jump processing method as described above, wherein the callback process further includes a repairing step of repairing the jump request to form a repair request after the local target is not detected, detecting the repair request, jumping to the local target if the local target is detected, and otherwise opening the jump request using a browser.
The skip processing method further includes a monitoring process, where the monitoring process monitors the pre-process, the skip process, and the callback process in real time, and repairs or alarms the failure when the failure is detected.
The jump processing apparatus of the present invention includes: an obtaining unit, configured to obtain a skip request in a pre-flow; the verification unit is used for verifying the legality of the jump request, if the request is legal, the jump flow is entered, and if the request is not legal, the callback flow is entered; the classification unit is used for classifying the jump request and dividing the jump request into corresponding processing threads; the analysis unit is used for analyzing the calling request in the jumping request, jumping is carried out according to the calling request if an effective value is obtained, and otherwise, the callback process is entered; and the detection unit is used for detecting the jump request, jumping to a local target if the local target is detected, and otherwise, opening the jump request by using a browser.
The jump processing apparatus as described above, further comprising: and the repairing unit is used for repairing the jump request to form a repairing request after the local target is not detected, detecting the repairing request, jumping to the local target if the local target is detected, and otherwise, opening the jump request by using a browser.
The jump processing apparatus as described above, further comprising: and the monitoring unit is used for monitoring the preposed flow, the skipping flow and the callback flow in real time and repairing or alarming the fault when the fault is detected.
The jump processing method and the jump processing equipment uniformly receive the jump request, process the jump request by multiple steps of verification, classification, analysis and the like, and can effectively screen and classify the jump request. According to whether the jump request is legal or not, classification analysis of the legal jump request and the like, targeted processing is achieved, and the overall processing efficiency is improved.
Drawings
FIG. 1 is a flowchart of an embodiment of a jump processing method according to the present invention;
FIG. 2 is a flowchart illustrating a jump processing method according to another embodiment of the present invention;
FIG. 3 is an exemplary system architecture to which embodiments of the invention may be applied;
FIG. 4 is a block diagram of a computer system that may be used to implement an electronic device according to an embodiment of the invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.
The invention discloses a jump processing method, which mainly comprises a preposition flow, a jump flow and a callback flow, and each part is explained below with reference to fig. 1.
The method mainly comprises two steps, namely an acquisition step and a verification step, wherein the acquisition step is used for acquiring a jump request, the verification step is used for verifying the legality of the jump request, if the verification result is legal, the jump flow is entered, and the callback flow is entered without rules. The definition of whether or not it is legal will be described below.
In the acquiring step, the acquired jump request may be automatically generated and sent by the system, or may be actively provided by the user as required. The format of the jump requests can be various, the content included in the jump requests can be various, and the content or the format of the content included in the jump requests can be acquired by the acquiring step through the same entry (or through the same way).
And then, in the verification step, at least verifying whether the jump request has the jump type, the jump destination and the parameters corresponding to the call request, and if so, verifying that the jump request is legal. A jump request with at least these three parameters is considered eligible. Of course, the specific contents can be adjusted as needed, and only three preferred installation modes of the present application are listed here.
The jump flow is described next, which can also be divided into two steps, a classification step and an analysis step. The classification step is to classify the jump requests and divide the jump requests into corresponding processing threads; certainly, the jump requests classified in the classification process are the jump requests verified to be qualified in the verification step, the verified and qualified requests have parameters corresponding to the jump types, and the jump types can be determined through the parameters, and common jump types include native jumps (local jumps), javascript responses (jumps), scheme jumps (scheduled jumps), third-party hoisting (jumps) and the like.
The jump requests are classified according to the types of jumps and divided into corresponding processing threads. A processing thread herein may refer to a thread in a processor into which data processing is divided, and they may be processed via the same process. Although in other embodiments, different processors may be partitioned.
In the present application, the same processor is used, and only different threads are entered, and it can also be understood that different processing manners are required for different jump requests.
After the classification step, classifying the jump request, and further performing an analysis step, wherein the analysis step is to analyze the call request in the jump request, and if an effective value is obtained, the jump is performed according to the call request, otherwise, the callback process is entered.
It can be understood that, because different threads are entered for processing, each thread has a corresponding parsing mode, and only this type of jump request is parsed, so that parsing time is greatly saved. It should also be understood from the description herein that the parsing step corresponds to the above classification step, that is, after the jump request is classified, each type of jump request has a special parsing step in its category, and the "one-to-one" parsing is performed on the jump request. That is, each thread has a corresponding parsing step, each hop type has a unique corresponding parsing step, and the parsing steps do not interfere with each other.
Of course, the above is an embodiment with a higher processing speed. Corresponding to the embodiment, the same parsing step is used for the classified jump requests, and since the jump requests are classified, the parsing step can know the type of the object to be parsed in advance, and there can be a form-specific adjustment parsing manner. For example, in the classification step, different types of jump requests are attached to corresponding labels, and the parsing step changes the parsing mode according to the labels. The implementation mode is slower in speed, complexity of the real problem is reduced, and follow-up maintenance and overhaul are more convenient.
The above-mentioned call request can be understood as the contents such as data, authority, parameters, etc. required when performing the jump, that is, the contents that need to be called to complete the jump action, and the call request is the request for using the contents.
Finally, a callback process is described, which comprises a detection step, wherein the callback process detects the jump request, if a local target is detected, the jump is carried out to the local target, otherwise, the jump request is opened by using a browser (webview).
The local target includes at least: local applications, local cache data, and local service requests. That is, the jump request is more "simple and direct", and the destination is directly marked, so long as the corresponding action is directly performed according to the jump request.
And if no destination is detected, the browser is used for opening, and here, as an attempt only, if the jump request includes a URL address and the like, the browser can be directly opened by using the browser, which is favorable for that the jump request is directly in a file format (such as gif format picture), and the browser is also possible to open. The jump information may contain content which is lost or not standard, and cannot be correspondingly processed by the verification step or the analysis step, but the jump information also comprises some content which can be called, so that the content to be displayed can be displayed by using a browser, and omission is avoided. It should be understood that the purpose of using browser open here is to avoid misses, but not necessarily to enable jumps. Once the jump request is opened through the browser, no display or corresponding execution operation is available, and the jump process fails here.
The following describes the parsing step by using a specific example, before explaining if the jump request is parsed, parameters in the jump request, that is, the jump type, the jump destination and the call request, are described, and in a specific embodiment, these parameters are mapped via a type parameter and a json parameter (short for JavaScript Object notification), that is, the jump request has a type parameter and a json parameter, more specifically, the type parameter is mapped with the corresponding jump type and jump destination, and the json parameter is mapped with the corresponding call request.
The type parameter and json parameter are only mappings of the jump type, the jump destination and the parameter corresponding to the call request, and the specific mapping manner is not limited as long as the verification step, the classification step, the analysis step and the like can be identified or judged. The content of the type parameter and the json parameter may be in a conventional manner, or may be set as needed, so long as a plurality of corresponding steps can be identified, and the method can be used in the present application.
In the analyzing step, the json parameter is analyzed, the purpose of the json parameter is to explain the corresponding call request, if a valid value is obtained, the jump is performed according to the information contained in the valid value, and if the valid value is not obtained, the callback process is entered. In the embodiment, the valid value corresponding to the analyzed json parameter is generally referred to as a key-value (key-value), and the key-value mentioned in the embodiment is one valid value in the call request obtained by analyzing the json parameter. That is, the key-value here is an embodiment of obtaining the valid value of the call request in the parsing step, and obtaining the key-value means that the parsing step obtains (parses) the call request and obtains (parses) the valid value of the call request, that is, the valid value that can be used for jumping. The valid value contains important information of the jump, at least including the content required for the jump as described above, according to which the jump can be implemented.
It should be noted that the parsing step obtains (parses out) the valid value if it has already parsed out the invocation request. If the invocation request is not resolved, then it must not be possible or a valid value, which is no longer distinguished. That is, there is no handle call request to be taken over, or the call request is parsed out but no valid value is obtained, both of which cases enter the callback flow.
Next, the analysis procedure will be described, which may be the analysis of different jump requests in different threads, or the analysis of different jump requests through one analysis procedure. The details have been already described above, and are not described herein again.
And the type and json parameters are used as a unified entry, and a rule for later calling is formulated. The situation that all positions and methods exist simultaneously is reduced, the system structure is simplified, the processing speed is improved, code fragments are optimized, constraint skipping of unified rules is carried out, the communication cost is reduced, and the rules are explicitly called.
Having described the detection step in the callback flow above, and then describing the repair step that may also be included in the callback flow, we have already known that, in the detection step, a jump request is detected, and if an ontology target is detected, a jump is performed, otherwise, the browser is used to open the jump. In some embodiments, a repair step is further added, see fig. 2, that is, after the local target is not detected, the repair step is performed first to repair the jump request, so as to form a repair request. Of course, the repairing of the skip request here means that in the detection step, in order to detect the skip request of the local target, there may be a variety of specific repairing manners, such as deleting redundant content, checking logic problems, and the like, which are detection manners known by those skilled in the art, and the description of the present application is omitted.
And then detecting the repair request, if a local target is detected, jumping to the local target, otherwise, opening the jump request by using a browser.
That is, the repair request is detected once, where the detection mode is the same as that in the detection step, but the difference is that the detection of the repair request does not enter the repair request again if the local target is still not detected, so as to avoid the loop operation, but directly uses the browser to open the repair request.
The foregoing has described the three parts of the pre-flow, the jump flow and the callback flow in the method, and it has been possible to implement efficient processing of the jump request, in this method, various types of jump requests are processed preferentially by the pre-flow, and there is no need to acquire the jump requests in a "trial" manner by using multiple receiving terminals, as in the prior art.
Based on the above three parts, the method preferably further comprises a fourth part: and monitoring the flow, wherein the monitoring flow monitors the preposition flow, the skipping flow and the callback flow in real time, and repairs or alarms the fault when the fault is detected.
For example, if a downtime (or called exception, crash) occurs, an exception trap (crashHandler) is invoked to perform internal digestion processing on the downtime (or called exception, crash).
In addition, the invention also discloses a jump processing device, which comprises: an obtaining unit, configured to obtain a skip request in a pre-flow; the verification unit is used for verifying the legality of the jump request, if the request is legal, the jump flow is entered, and if the request is not legal, the callback flow is entered; the classification unit is used for classifying the jump request and dividing the jump request into corresponding processing threads; the analysis unit is used for analyzing the calling request in the jumping request, jumping is carried out according to the calling request if an effective value is obtained, and otherwise, the callback process is entered; and the detection unit is used for detecting the jump request, jumping to a local target if the local target is detected, and otherwise, opening the jump request by using a browser.
Of course, also includes: and the repairing unit is used for repairing the jump request to form a repairing request after the local target is not detected, detecting the repairing request, jumping to the local target if the local target is detected, and otherwise, opening the jump request by using a browser.
And further comprising: and the monitoring unit is used for monitoring the preposed flow, the skipping flow and the callback flow in real time and repairing or alarming the fault when the fault is detected.
Referring now to fig. 3, an exemplary system architecture in which embodiments of the present application may be applied is shown with a system 700, which system 700 may include electronic devices 701, 702, a network 703, and servers 704, 705, 706, and 707. The network 703 is the medium used to provide communications links between the electronic devices 701, 702 and the servers 704, 705, 706, 707. The network 703 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user 710 may use the electronic devices 701, 702 to interact with the servers 704, 705, 706, 707 via the network 703 to access various services, e.g. the user may click, initiate a jump request, be processed by a subsequent pre-flow reception. This of course also does not leave the acquisition unit for the jump request. The jump request actively generated by the user 710 is one way in which the jump request may be generated.
The electronic devices 701 and 702 may be installed with applications corresponding to the server, and the applications may at least generate and send out the jump request, and of course, the jump request may be processed inside the application or sent outside the application, that is, the jump processing method and apparatus according to the present invention may be located inside the application or inside the application, which is a general method. For example, the jump processing method may be executed inside a certain mobile phone APP, and a corresponding device (the device may be virtual) is also correspondingly provided, so that the jump among various function modules inside the mobile phone APP is realized.
The mobile phone APP can also send the jump request, for example, to the mobile phone system, and the mobile phone system executes the jump processing method disclosed by the invention according to the jump request, so that the interactive jump between the mobile phone APP and the mobile phone system can be realized.
The method can also be used for interaction between the mobile phone APPs, namely, one mobile phone APP sends a jump request to the other mobile phone APP, and the other mobile phone APP jumps by using the method of the invention, so that the jump of two mobile phone APP pieces is realized.
The electronic devices 701, 702 may be a variety of electronic devices including, but not limited to, personal computers, smart phones, smart televisions, tablet computers, personal digital assistants, electronic book readers, and the like. The servers 704, 705, 706, 707 may be servers that provide various services. The server may provide a service in response to a service request from a user, for example, providing a commodity URL, and may also perform subsequent operations, and even the above-mentioned e-commerce commodity information distribution system may be provided in or attached to the server 704, 705, 706, 707.
It should be noted that the jump processing method of the present invention is implemented by a server through the internet, and may be integrated in an electronic device, and the function may be implemented without networking.
Referring now to FIG. 4, shown is a block diagram of a computer system 800 suitable for use in implementing the electronic device of an embodiment of the present application.
As shown in fig. 4, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary. In particular, the processes described above with reference to fig. 1-2 may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the disclosure may include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing program code for performing the methods of fig. 1-2. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811.
The construction, features and functions of the present invention are described in detail in the embodiments illustrated in the drawings, which are only preferred embodiments of the present invention, but the present invention is not limited by the drawings, and all equivalent embodiments modified or changed according to the idea of the present invention should fall within the protection scope of the present invention without departing from the spirit of the present invention covered by the description and the drawings.
Claims (10)
1. A jump processing method is characterized by comprising the following steps:
a pre-flow, a skip flow and a callback flow; wherein,
the pre-process comprises the following steps:
an obtaining step, obtaining a jump request;
a verification step, namely verifying the legality of the jump request, if the request is legal, entering a jump flow, and otherwise, entering a callback flow;
the skipping process comprises the following steps:
classifying, namely classifying the jump requests and dividing the jump requests into corresponding processing threads;
analyzing, namely analyzing a calling request in the jumping request, jumping according to the calling request if an effective value is obtained, and entering the callback flow if the effective value is not obtained;
the callback process comprises the following steps:
and a detection step, namely detecting the jump request, jumping to a local target if the local target is detected, and otherwise opening the jump request by using a browser.
2. The jump processing method according to claim 1,
the verifying step includes:
and at least verifying whether the jump request has a jump type, a jump destination and parameters corresponding to the call request, and if the jump request has the parameters, determining that the jump request is legal.
3. The jump processing method according to claim 2,
the jump request at least comprises a type parameter and a json parameter, wherein,
the type parameter is mapped with the corresponding jump type and the jump destination;
and the json parameter is mapped with the corresponding calling request.
4. The jump processing method according to claim 3,
in the analyzing step, the json parameter is analyzed, if an effective value is obtained, skipping is carried out according to the effective value, and if the effective value is not obtained, the callback process is started.
5. The jump processing method according to claim 1,
the local target includes at least: any one of a local application, local cache data, and a local service request.
6. The jump processing method according to any one of claims 1 to 5,
and the callback flow also comprises a repairing step, namely repairing the jump request after the local target is not detected to form a repairing request, detecting the repairing request, jumping to the local target if the local target is detected, and otherwise opening the jump request by using a browser.
7. The jump processing method according to any one of claims 1 to 5,
the method also comprises a monitoring flow, wherein the monitoring flow monitors the preposition flow, the skip flow and the callback flow in real time and repairs or alarms the fault when the fault is detected.
8. A jump processing apparatus characterized by comprising:
an obtaining unit, configured to obtain a skip request in a pre-flow;
the verification unit is used for verifying the legality of the jump request, if the request is legal, the jump flow is entered, and if the request is not legal, the callback flow is entered;
the classification unit is used for classifying the jump request and dividing the jump request into corresponding processing threads;
the analysis unit is used for analyzing the calling request in the jumping request, jumping is carried out according to the calling request if an effective value is obtained, and otherwise, the callback process is entered;
and the detection unit is used for detecting the jump request, jumping to a local target if the local target is detected, and otherwise, opening the jump request by using a browser.
9. The jump processing apparatus according to claim 8, further comprising:
and the repairing unit is used for repairing the jump request to form a repairing request after the local target is not detected, detecting the repairing request, jumping to the local target if the local target is detected, and otherwise, opening the jump request by using a browser.
10. The jump processing apparatus according to claim 8 or 9, further comprising:
and the monitoring unit is used for monitoring the preposed flow, the skipping flow and the callback flow in real time and repairing or alarming the fault when the fault is detected.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810027229.2A CN108234665B (en) | 2018-01-11 | 2018-01-11 | Jump processing method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810027229.2A CN108234665B (en) | 2018-01-11 | 2018-01-11 | Jump processing method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108234665A true CN108234665A (en) | 2018-06-29 |
| CN108234665B CN108234665B (en) | 2021-07-09 |
Family
ID=62640169
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810027229.2A Active CN108234665B (en) | 2018-01-11 | 2018-01-11 | Jump processing method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108234665B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140297402A1 (en) * | 2013-04-02 | 2014-10-02 | Media Group Ltd. | Methods and Systems for Promoting and Tracking Digital Offers across Multiple Devices |
| CN104346267A (en) * | 2013-08-08 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and device for generating program bug positioning information |
| CN106095797A (en) * | 2016-05-31 | 2016-11-09 | 北京京东尚科信息技术有限公司 | The data display method of handheld terminal, display system and client |
| CN106095549A (en) * | 2016-06-07 | 2016-11-09 | 中国建设银行股份有限公司 | The jump method of a kind of Mobile solution App and redirect device |
| CN106874035A (en) * | 2017-01-11 | 2017-06-20 | 深圳中顺易金融服务有限公司 | One kind is applied for updating（app）The method and its framework of built-in H5 |
-
2018
- 2018-01-11 CN CN201810027229.2A patent/CN108234665B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140297402A1 (en) * | 2013-04-02 | 2014-10-02 | Media Group Ltd. | Methods and Systems for Promoting and Tracking Digital Offers across Multiple Devices |
| CN104346267A (en) * | 2013-08-08 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and device for generating program bug positioning information |
| CN106095797A (en) * | 2016-05-31 | 2016-11-09 | 北京京东尚科信息技术有限公司 | The data display method of handheld terminal, display system and client |
| CN106095549A (en) * | 2016-06-07 | 2016-11-09 | 中国建设银行股份有限公司 | The jump method of a kind of Mobile solution App and redirect device |
| CN106874035A (en) * | 2017-01-11 | 2017-06-20 | 深圳中顺易金融服务有限公司 | One kind is applied for updating（app）The method and its framework of built-in H5 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108234665B (en) | 2021-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11271955B2 (en) | Platform and method for retroactive reclassification employing a cybersecurity-based global data store | |
| US11316900B1 (en) | System and method for automatically prioritizing rules for cyber-threat detection and mitigation | |
| US20190207966A1 (en) | Platform and Method for Enhanced Cyber-Attack Detection and Response Employing a Global Data Store | |
| US9690606B1 (en) | Selective system call monitoring | |
| US11240275B1 (en) | Platform and method for performing cybersecurity analyses employing an intelligence hub with a modular architecture | |
| EP4060958B1 (en) | Attack behavior detection method and apparatus, and attack detection device | |
| US9519789B2 (en) | Identifying security vulnerabilities related to inter-process communications | |
| CN106790291B (en) | Intrusion detection prompting method and device | |
| CN111586005B (en) | Scanner scanning behavior identification method and device | |
| CN112653618A (en) | Gateway registration method and device of micro-service application API endpoint | |
| US11947669B1 (en) | System and method for circumventing evasive code for cyberthreat detection | |
| US10291492B2 (en) | Systems and methods for discovering sources of online content | |
| CN108764374B (en) | Image classification method, system, medium, and electronic device | |
| US7971054B1 (en) | Method of and system for real-time form and content classification of data streams for filtering applications | |
| CN113055199A (en) | Gateway access method and device and gateway equipment | |
| GB2542140B (en) | Controlling access to web resources | |
| CN112994934B (en) | Data interaction method, device and system | |
| US11985149B1 (en) | System and method for automated system for triage of cybersecurity threats | |
| CN112468840A (en) | Tamper-proof system and method for third-party EPG server in IPTV system | |
| CN108234665B (en) | Jump processing method and equipment | |
| CN110177096B (en) | Client authentication method, device, medium and computing equipment | |
| CN114827157B (en) | Cluster task processing method, device and system, electronic equipment and readable medium | |
| CN114461230A (en) | Gray scale publishing method, device, equipment and medium | |
| CN114461909A (en) | Information processing method, information processing apparatus, electronic device, and storage medium | |
| CN112929321B (en) | Authentication method, device and terminal equipment |
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 | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Liu Feng Inventor after: Sui Guo Dong Inventor after: Liu Chao Inventor after: Sun Faxin Inventor before: Sun Faxin |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |