CN109922132B - Form request processing method and device, electronic equipment and storage medium - Google Patents
Form request processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN109922132B CN109922132B CN201910048698.7A CN201910048698A CN109922132B CN 109922132 B CN109922132 B CN 109922132B CN 201910048698 A CN201910048698 A CN 201910048698A CN 109922132 B CN109922132 B CN 109922132B
- Authority
- CN
- China
- Prior art keywords
- request
- random identifier
- page
- current page
- form request
- 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
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to the field of computer technologies, and in particular, to a form request processing method, a form request processing apparatus, an electronic device, and a storage medium. The method comprises the following steps: judging whether a form request exists in a current page of a client; if the current page of the client has a form request, extracting a random identifier configured in advance for the current page; and binding the random identifier and the form request and sending the bound random identifier and the form request to a server side so that the server side judges whether to process the form request according to the random identifier. The method and the device can enable the server to judge whether the received form request is repeated according to the random identifier, and further effectively prevent the form request from being processed repeatedly.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a form request processing method, a form request processing apparatus, an electronic device, and a storage medium.
Background
When a user uses an application program on a mobile terminal, page operation for submitting a form is often involved. Especially for financial applications, in order to prevent the user from repeatedly submitting the form on the interface related to the amount of money or the transaction, some measures are usually taken on the interactive interface of the client, for example, after the user clicks the physical or virtual key to submit the form, a full-screen shielding waiting (loading) pattern can be enabled immediately to prevent the user from continuing to click the submit button. However, because the diversity of the mobile terminal models used by the user and the complexity of the UI adaptation are high, if the UI interface is stuck or the adaptation is wrong, the probability that the submit button can be repeatedly clicked is high, and thus the reliability of the scheme is low.
In addition, for the server side, in order to prevent the user from repeatedly submitting the form, the form parameters and the submission time can be detected at the server side, and the rejection processing is performed on the form submission with the same request parameters and the same request time interval (within 1-2 s). Although the method can prevent repeated submission caused by misoperation of the client in a short time, the method cannot effectively screen whether the user submits a new list or a repeated list.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a form request processing method, a form request processing apparatus, an electronic device, and a storage medium, which overcome at least to some extent the limitations and disadvantages of the related art, such that a form request is repeatedly processed.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to a first aspect of the embodiments of the present disclosure, there is provided a method for preventing a form from being repeatedly submitted, the method including:
judging whether a form request exists in a current page of a client;
if the current page of the client has a form request, extracting a random identifier configured in advance for the current page;
and binding the random identifier and the form request and sending the bound random identifier and the form request to a server side so that the server side can judge whether to process the form request according to the random identifier.
In an exemplary embodiment of the present disclosure, after the random identifier is bound with the form request and sent to a server, the method further includes:
if feedback information requested by the server side for the form is received, the feedback information is displayed on a current page of the client side;
wherein the feedback information comprises: any prompt information of form completion information, form submission failure information or form repeated submission information.
In an exemplary embodiment of the present disclosure, before determining whether there is a form request on a current page of a client, the method further includes: configuring a random identifier for the current page, including:
judging whether a page element for submitting a form exists in a current page or not;
if the current page has page elements for submitting the form, sending a random identifier distribution request to the server to acquire a random identifier matched with the current page; or
And if the current page has page elements for submitting the form, extracting a random identifier from a local preset identifier list, and matching the random identifier with the current page.
In an exemplary embodiment of the present disclosure, the method further includes:
and if the current page has updating operation, updating the random identifier, and matching the updated random identifier with the updated current page.
According to a second aspect of the embodiments of the present disclosure, there is provided a form request processing method, the method including:
receiving a form request of a client, and extracting a random identifier bound with the form request;
extracting a current value corresponding to the form request from a preset database according to the random identifier;
judging whether the form request is a repeated request according to the current value corresponding to the form request, and generating corresponding feedback information;
and sending the feedback information to the client.
In an exemplary embodiment of the present disclosure, the determining whether the form request is a repeated request according to a current value corresponding to the form request, and generating corresponding feedback information includes:
if the current value is empty, modifying the current value into a first numerical value, modifying the current value into a second numerical value after the form request is completed, and generating corresponding feedback information of successful request; or
And if the current value is the second numerical value, generating feedback information repeatedly submitted by the form.
According to a third aspect of the embodiments of the present disclosure, there is provided a form request processing apparatus including:
the request monitoring module is used for judging whether a form request exists in the current page of the client;
the identification extraction module is used for extracting a random identification configured in advance by the current page if the current page of the client has a form request;
and the request sending module is used for binding the random identifier and the form request and sending the bound random identifier and the form request to a server so that the server judges whether to process the form request according to the random identifier.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a form request processing apparatus including:
the request receiving module is used for receiving a form request of a client and extracting a random identifier bound with the form request;
the identification verification module is used for extracting a current value corresponding to the form request from a preset database according to the random identification;
the request feedback module is used for judging whether the form request is a repeated request according to the current value corresponding to the form request and generating corresponding feedback information;
and the feedback information sending module is used for sending the feedback information to the client.
According to a fifth aspect of the present disclosure, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the above-described form request processing method.
According to a sixth aspect of the present disclosure, an electronic terminal comprises:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to execute any one of the above form request processing methods.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
in an embodiment of the present disclosure, in the form request processing method, a random identifier is configured for a page in advance, and when a form request is submitted in the page, the random identifier is bound with the form request, so that a server side can determine whether a received form request is repeated according to the random identifier, and further, the server side is effectively prevented from repeatedly processing the same form request.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It should be apparent that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived by those of ordinary skill in the art without inventive effort.
FIG. 1 is a diagram that schematically illustrates a method for form request processing, in an exemplary embodiment of the disclosure;
FIG. 2 is a diagram schematically illustrating another form request processing method in an exemplary embodiment of the present disclosure;
FIG. 3 is a block diagram schematically illustrating a form request processing apparatus according to an exemplary embodiment of the present disclosure;
fig. 4 schematically illustrates a composition diagram of a form request processing apparatus in an exemplary embodiment of the present disclosure;
fig. 5 schematically illustrates another schematic diagram of a form request processing apparatus in an exemplary embodiment of the present disclosure;
fig. 6 schematically illustrates a program product of a form request processing method in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The exemplary embodiment first provides a form request processing method. Referring to fig. 1, the method may include the steps of:
step S11, judging whether a form request exists in the current page of the client;
step S12, if the current page of the client has a form request, extracting a random identifier pre-configured for the current page;
and S13, binding the random identifier and the form request and sending the bound random identifier and the form request to a server.
According to the form request processing method, the random identifier is configured for the page in advance, and when the form request is submitted in the page, the random identifier is bound with the form request, so that the server side can judge whether the received form request is repeated according to the random identifier, and the server side is effectively prevented from repeatedly processing the same form request.
Hereinafter, the respective steps of the above-described method in the present exemplary embodiment will be described in more detail with reference to the drawings and examples.
When a user uses a terminal device to browse a web page or uses an application program, the user often involves an operation of submitting a form. For example, an account registration application is submitted on a user registration page, payment is submitted on a shopping page, and so on. At this time, such a page may be preconfigured with a random identity. Specifically, the method described above may include:
and S10, configuring a random identifier for the current page.
In this exemplary embodiment, specifically, for the terminal device on the user side, the method may include:
step S101, judging whether a page element for submitting a form exists in a current page or not;
step S102, if the current page has page elements for submitting forms, sending a random identifier distribution request to the server side to obtain a random identifier matched with the current page; or
Step S103, if the current page has page elements for submitting the form, extracting a random identifier from a local preset identifier list, and matching the random identifier with the current page.
For a terminal device at a user side, for example, an intelligent terminal such as a mobile phone, a tablet computer, or a notebook computer, a user often involves a requirement and an operation of submitting a form during a process of accessing the internet, for example, browsing a web page and using an application program. At this time, the page elements in the current view page may be captured and identified first, and it is determined whether there is a page element for submitting the form.
For example, a page may generally include elements such as characters, pictures, scroll bars, input boxes, and buttons, and each element in the page may be identified according to a tag or an attribute value of each element. When the user switches to a page, all elements in the current page can be read, and the type attribute of each element is acquired, so that the page elements used for submitting the form in the current page can be identified according to the attribute values.
For example, when a user registers the user in a friend-making website, the user needs to fill in registration information in a corresponding registration page, a "submit" or "confirm" button exists in a current view page, and when a page element corresponding to the "submit" or "confirm" button in the page is identified, it can be determined that a page element for submitting a form exists in the current view page. For example, a user clicking a "submit" or "confirm" button via an input device triggers the submission of a registration form to the server for processing by the server. Or, when the user purchases an item at the shopping website, the user needs to confirm the shopping information on the payment interface, fill in the corresponding payment password, and click the "submit" or "confirm" button, and then the user triggers the submission of the payment form to the server, so that the server processes the payment form.
Therefore, for the current page where the user is located, the page element of the current page can be firstly identified, and whether the page element for submitting the form exists or not can be judged. And if the elements for submitting the form exist, configuring a random identifier for the current page. Or when a user enters a service page, a random identifier can be generated for the page.
For the random identification, a fixed length random number, or a combination of a number and a letter, or a combination of a number, a letter and a preset symbol may be used. For example, the random identifier may be 58462054,5f6r3g4m, or 5gsd5&h ^ and the like. Of course, in other exemplary embodiments of the present disclosure, the random identifier may be configured to have other lengths or formats, for example, the random identifier is set to be 256 bits, etc.; the present disclosure does not specifically limit the specific expression of the random identifier.
In addition, the random identifier may also be allocated to the page by the server, and when the terminal side recognizes that the current page has a page element for submitting the form, the terminal side sends a request for requesting the random identifier to the server, and when the server side returns the random identifier, the random identifier and the current page establish a corresponding relationship or bind. Or, the terminal side may also set an identifier list in advance locally, and when detecting that an element for submitting a form exists in the current page, extract a random identifier to the identifier list in a random or sequential manner, and bind the random identifier with the current page. By configuring the random identifier for the page according to the identification result of the page element, the random identifier can be prevented from being distributed to all pages, and the execution accuracy of the random identifier distribution action is ensured.
And step S11, judging whether the current page of the client has a form request or not.
In this exemplary embodiment, for the terminal, it may be determined whether the user sends a form request in the current page according to a trigger operation for a page element in the current page. For example, on a trading page, when a user clicks or selects a corresponding virtual control for "submit" or "confirm", it is determined that a form request has occurred for the current page.
And step S12, if the form request exists in the current page of the client, extracting a random identifier pre-configured for the current page.
In this exemplary embodiment, for the terminal, after recognizing that the form request occurs in the current service page, the content of the random identifier previously allocated to the current service page may be extracted. For example, in the payment interface of a shopping website, when the user clicks on a page element confirming the payment amount in the page, or inputs a password, or clicks on a "confirm" button, the random identifier corresponding to the current page may be extracted. By extracting the random identifier only when the current page submits the form request, the random identifier can be prevented from being extracted to have adverse effects on other operations in the page.
And S13, binding the random identifier and the form request and sending the bound random identifier and the form request to a server side so that the server side can judge whether to process the form request according to the random identifier.
In this exemplary embodiment, after extracting the specific random identifier, the random identifier may be bound with the form request, and sent to the server side along with the form. For example, for Form forms, a random identifier can be added as a submission term for an Form element in the Form dataset for recognition by the server. Alternatively, the random identifier may be added to the url address as a suffix and transmitted to the server side. Or, the random identifier is added to the action attribute of the Form as a part of the attribute value, so that the server side can conveniently identify the Form request according to the random identifier.
Based on the above, in the present exemplary embodiment, the method described above may further include: and if the current page has updating operation, updating the random identifier, and matching the updated random identifier with the updated current page.
For example, when the user actively exits the current service page, the random identifier corresponding to the service page may be deleted together. Or when the user refreshes the current service page, the corresponding random identifier is updated. That is, the random identification remains unchanged until the page is exited or refreshed.
And step S14, if feedback information requested by the server side for the form is received, the feedback information is displayed on a current page of the client side.
In this exemplary embodiment, the feedback information may include: any prompt message of form completion information, form submission failure information or form repeated submission information.
For example, after the user submits a form request for registering an account, the server may perform feedback according to the form data after receiving the form data. For example, when the account name is determined not to be duplicated, information of successful registration may be returned to the client. The terminal can display the information on the interactive interface when receiving the information. Or, when the terminal submits the payment request form for multiple times, the server side can feed back a prompt message submitted repeatedly to the terminal after recognizing multiple repeated form requests of the terminal, and the terminal displays the prompt message. By configuring a unique random identifier for the page, the server can accurately judge whether the form request is repeated according to the random identifier.
The present exemplary embodiment further provides a form request processing method, and as shown in fig. 2, the method may include the following steps:
step S21, receiving a form request of a client, and extracting a random identifier bound with the form request;
s22, extracting a current value corresponding to the form request from a preset database according to the random identifier;
step S23, judging whether the form request is a repeated request according to the current value corresponding to the form request, and generating corresponding feedback information;
and step S24, sending the feedback information to the client.
In the present exemplary embodiment, for the server side, after receiving the form request from the user terminal, the random identifier corresponding to the form request may be extracted. And judging the specific state corresponding to the form request according to the random identifier.
Specifically, if the current value corresponding to the form request is empty, the current value is modified into a first numerical value, the current value is modified into a second numerical value after the form request is completed, and corresponding feedback information of successful request is generated; or if the current value is the second numerical value, generating feedback information of repeated submission of the form.
For example, after receiving a first form request for a service page, the server may store a corresponding random identifier as a key in a redis database, and set an initial value to false. And when the server side completes the processing of the corresponding form request, the corresponding value is modified to true, so that the current state corresponding to the form request is marked.
At this time, if the server receives the form request for the service page again, the random identifier is used as a key, the corresponding current value is read from the redis database, and if the read current value is true, it can be determined that the form request is a repeated form request. The form request is not processed. Therefore, repeated form requests of the user are effectively avoided being processed.
In other exemplary embodiments of the present disclosure, based on the above, when the server receives a form request for a service page, the server uses the random identifier as a key to read a corresponding current value from a redis database, and if the read current value is false, it indicates that the current form request is a repeated request, but the server does not complete processing of the preamble form request. At this time, the current form request may be added to a predetermined waiting list, and a mapping relationship between the current form request and the preceding form request may be established. And when detecting that the server end completes the processing of the preorder form request and generates feedback information, returning the feedback information of the current list request according to the mapping relation. Therefore, the server side avoids repeated processing of the form requests repeatedly sent by the client side.
In summary, in the method in the exemplary embodiment, the server side may determine, after receiving the form request, whether the currently received form is a form request repeatedly sent by the user terminal according to the random identifier by allocating the random identifier to the service page in advance, and perform corresponding processing when determining that the form request is repeated by the user. Therefore, the cooperative verification of the client and the server in the form request processing process is realized, and the problem that the single end verifies the repeated form request is unreliable is avoided.
It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc. Additionally, it will also be readily appreciated that the steps may be performed synchronously or asynchronously, e.g., among multiple modules/processes/threads.
Further, in the present exemplary embodiment, a form request processing apparatus 30 is also provided. Referring to fig. 3, the apparatus 30 may include: a request monitoring module 301, an identity extraction module 302 and a request sending module 303. Wherein the content of the first and second substances,
the request monitoring module 301 may be configured to determine whether a form request exists on a current page of a client.
The identifier extracting module 302 may be configured to extract a random identifier preconfigured in the current page if a form request exists in the current page of the client.
The request sending module 303 may be configured to bind the random identifier and the form request and send the bound random identifier and the form request to a server, so that the server determines whether to process the form request according to the random identifier.
Further, in the present exemplary embodiment, a form request processing apparatus 40 is also provided. Referring to fig. 4, the apparatus 40 may include: a request receiving module 401, an identification verification module 402, a request feedback module 403, and a feedback information sending module 404. Wherein the content of the first and second substances,
the request receiving module 401 may be configured to receive a form request from a client and extract a random identifier bound to the form request.
The identifier verification module 402 may be configured to extract a current value corresponding to the form request from a preset database according to the random identifier.
The request feedback module 403 may be configured to determine whether the form request is a repeated request according to a current value corresponding to the form request, and generate corresponding feedback information.
The feedback information sending module 404 may be configured to send the feedback information to the client.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units. The components shown as modules or units may or may not be physical units, i.e. may be located in one place or may be distributed over a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the wood-disclosed scheme. One of ordinary skill in the art can understand and implement it without inventive effort.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method for preventing form duplicate submission is also provided.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 5. The electronic device 600 shown in fig. 5 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 5, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: the at least one processing unit 610, the at least one memory unit 620, and a bus 630 that couples the various system components including the memory unit 620 and the processing unit 610.
Wherein the memory unit stores program code that may be executed by the processing unit 610 to cause the processing unit 610 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary method" of this specification. For example, the processing unit 610 may execute step S11 shown in fig. 1 to determine whether there is a form request on the current page of the client; step S12, if the current page of the client has a form request, extracting a random identifier pre-configured for the current page; step S13, binding the random identifier and the form request and sending the bound random identifier and the form request to a server so that the server judges whether to process the form request according to the random identifier; or executing step S21 shown in fig. 2, receiving a form request of a client, and extracting a random identifier bound to the form request; s22, extracting a current value corresponding to the form request from a preset database according to the random identifier; step S23, judging whether the form request is a repeated request according to the current value corresponding to the form request, and generating corresponding feedback information; and step S24, sending the feedback information to the client.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM) 6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may comprise an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. As shown, the network adapter 660 communicates with the other modules of the electronic device 600 over the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 6, a program product 800 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this respect, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (9)
1. A form request processing method is characterized by comprising the following steps:
judging whether a form request exists in a current page of a client;
if the current page of the client has a form request, extracting a random identifier configured in advance for the current page;
binding the random identifier and the form request and sending the random identifier and the form request to a server side so that the server side judges whether to process the form request according to the random identifier; the server extracts a current value corresponding to the form request from a preset database according to the random identifier; judging whether the form request is a repeated request according to a current value corresponding to the form request;
before determining whether the form request exists on the current page of the client, the method further includes: configuring a random identifier for a current page, including:
judging whether a page element for submitting a form exists in a current page or not;
if the current page has page elements for submitting the form, sending a random identifier distribution request to the server to acquire a random identifier matched with the current page; or
And if the current page has page elements for submitting the form, extracting a random identifier from a local preset identifier list, and matching the random identifier with the current page.
2. The method of claim 1, wherein after the binding and sending the random identifier and the form request to a server, the method further comprises:
if feedback information requested by the server side for the form is received, the feedback information is displayed on a current page of the client side;
wherein the feedback information comprises: any prompt information of form completion information, form submission failure information or form repeated submission information.
3. The method of claim 1, further comprising:
and if the current page has updating operation, updating the random identifier, and matching the updated random identifier with the updated current page.
4. A form request processing method, comprising:
receiving a form request of a client, and extracting a random identifier bound with the form request;
extracting a current value corresponding to the form request from a preset database according to the random identifier;
judging whether the form request is a repeated request according to a current value corresponding to the form request, and generating corresponding feedback information;
sending the feedback information to the client;
wherein the configuration of the random identifier comprises: judging whether a page element for submitting a form exists in a current page or not; if the current page has page elements for submitting the form, sending a random identifier distribution request to a server side to obtain a random identifier matched with the current page; or, if the current page has a page element for submitting a form, extracting a random identifier from a local preset identifier list, and matching the random identifier with the current page.
5. The method of claim 4, wherein the determining whether the form request is a repeat request according to the current value corresponding to the form request and generating corresponding feedback information comprises:
if the current value is empty, modifying the current value into a first numerical value, modifying the current value into a second numerical value after the form request is completed, and generating corresponding feedback information of successful request; or
And if the current value is the second numerical value, generating feedback information repeatedly submitted by the form.
6. A form request processing apparatus, comprising:
the request monitoring module is used for judging whether a form request exists in the current page of the client;
the identification extraction module is used for extracting a random identification configured in advance by the current page if the current page of the client has a form request;
the request sending module is used for binding the random identifier and the form request and sending the bound random identifier and the form request to a server so that the server can judge whether to process the form request according to the random identifier;
the device is further configured to configure a random identifier for the current page, including: judging whether a page element for submitting a form exists in a current page or not; if the current page has page elements for submitting the form, sending a random identifier distribution request to the server to acquire a random identifier matched with the current page; or if the current page has page elements for submitting the form, extracting a random identifier from a local preset identifier list, and matching the random identifier with the current page.
7. A form request processing apparatus, comprising:
the request receiving module is used for receiving a form request of a client and extracting a random identifier bound with the form request;
the identification verification module is used for extracting a current value corresponding to the form request from a preset database according to the random identification;
the request feedback module is used for judging whether the form request is a repeated request according to a current value corresponding to the form request and generating corresponding feedback information;
the feedback information sending module is used for sending the feedback information to the client;
wherein the configuration of the random identifier comprises: judging whether a page element for submitting a form exists in a current page or not; if the current page has page elements for submitting the form, sending a random identifier distribution request to a server side to obtain a random identifier matched with the current page; or, if the current page has a page element for submitting a form, extracting a random identifier from a local preset identifier list, and matching the random identifier with the current page.
8. A storage medium storing a computer program executable by a processor to perform the form request processing method according to any one of claims 1 to 5.
9. An electronic terminal, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the form request processing method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910048698.7A CN109922132B (en) | 2019-01-18 | 2019-01-18 | Form request processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910048698.7A CN109922132B (en) | 2019-01-18 | 2019-01-18 | Form request processing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109922132A CN109922132A (en) | 2019-06-21 |
| CN109922132B true CN109922132B (en) | 2023-04-11 |
Family
ID=66960447
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910048698.7A Active CN109922132B (en) | 2019-01-18 | 2019-01-18 | Form request processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109922132B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110472173A (en) * | 2019-08-19 | 2019-11-19 | 珠海格力电器股份有限公司 | The method, apparatus and storage medium that list is submitted |
| CN110855655B (en) * | 2019-11-06 | 2021-12-24 | 北京字节跳动网络技术有限公司 | Information verification method, device, equipment and storage medium |
| CN110992131B (en) * | 2019-11-20 | 2024-04-19 | 北京皮尔布莱尼软件有限公司 | Form processing method, form processing device and storage medium |
| CN111770171B (en) * | 2020-06-29 | 2023-05-02 | 浪潮通用软件有限公司 | Multi-page function session period state management method in micro-service mode |
| CN112256696A (en) * | 2020-09-30 | 2021-01-22 | 上海艾融软件股份有限公司 | Form data processing method, device, equipment and storage medium |
| CN112256776B (en) * | 2020-10-16 | 2022-11-22 | 武汉悦学帮网络技术有限公司 | Form repeated submission detection method and device, computer equipment and storage medium |
| CN112905163B (en) * | 2021-03-15 | 2024-04-16 | 上海万物新生环保科技集团有限公司 | Form submitting method and device |
| CN113377855A (en) * | 2021-06-25 | 2021-09-10 | 芜湖雄狮汽车科技有限公司 | Method and device for preventing form from being resubmitted, electronic equipment and storage medium |
| CN113852474B (en) * | 2021-09-23 | 2024-04-05 | 京东方科技集团股份有限公司 | Task processing method, gateway, computer readable storage medium and electronic device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6237035B1 (en) * | 1997-12-18 | 2001-05-22 | International Business Machines Corporation | System and method for preventing duplicate transactions in an internet browser/internet server environment |
| CN106161466A (en) * | 2016-08-30 | 2016-11-23 | 迈普通信技术股份有限公司 | WEB server and list submit safety interacting method to |
| CN107147659A (en) * | 2017-06-01 | 2017-09-08 | 上海斐讯数据通信技术有限公司 | A kind of method and system for preventing to repeat |
| CN107306288A (en) * | 2016-04-22 | 2017-10-31 | 深圳市医点通互联网技术股份有限公司 | A kind of submission generic operation processing method and system applied to portable medical |
| CN108985092A (en) * | 2017-06-05 | 2018-12-11 | 北京京东尚科信息技术有限公司 | Submit filter method, device, electronic equipment and the storage medium of request |
| CN109003071A (en) * | 2018-05-31 | 2018-12-14 | 阿里巴巴集团控股有限公司 | Method of payment, device and equipment |
| CN109144625A (en) * | 2017-06-28 | 2019-01-04 | 东软集团股份有限公司 | It is anti-to repeat to submit methods, devices and systems |
-
2019
- 2019-01-18 CN CN201910048698.7A patent/CN109922132B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6237035B1 (en) * | 1997-12-18 | 2001-05-22 | International Business Machines Corporation | System and method for preventing duplicate transactions in an internet browser/internet server environment |
| CN107306288A (en) * | 2016-04-22 | 2017-10-31 | 深圳市医点通互联网技术股份有限公司 | A kind of submission generic operation processing method and system applied to portable medical |
| CN106161466A (en) * | 2016-08-30 | 2016-11-23 | 迈普通信技术股份有限公司 | WEB server and list submit safety interacting method to |
| CN107147659A (en) * | 2017-06-01 | 2017-09-08 | 上海斐讯数据通信技术有限公司 | A kind of method and system for preventing to repeat |
| CN108985092A (en) * | 2017-06-05 | 2018-12-11 | 北京京东尚科信息技术有限公司 | Submit filter method, device, electronic equipment and the storage medium of request |
| CN109144625A (en) * | 2017-06-28 | 2019-01-04 | 东软集团股份有限公司 | It is anti-to repeat to submit methods, devices and systems |
| CN109003071A (en) * | 2018-05-31 | 2018-12-14 | 阿里巴巴集团控股有限公司 | Method of payment, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109922132A (en) | 2019-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109922132B (en) | Form request processing method and device, electronic equipment and storage medium | |
| WO2018019168A1 (en) | Method and apparatus for awakening application by means of mobile browser | |
| CN108073429B (en) | Payment mode configuration method, device, equipment and storage medium | |
| CN111242462B (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN114239504A (en) | Form configuration method, device, equipment, readable storage medium and program product | |
| CN107295086B (en) | Cluster session loss prevention method and system | |
| WO2016090328A1 (en) | Processing unstructured messages | |
| CN108346095B (en) | Management and control method, device and equipment of combined system and computer readable storage medium | |
| CN111861598A (en) | Object display method and device, electronic equipment and readable medium | |
| US20200294117A1 (en) | Method and device for fast order processing | |
| US11861214B2 (en) | Memory device forensics and preparation | |
| CN110807056A (en) | Excel-based report processing method, Excel-based report processing device, Excel-based report processing medium and electronic equipment | |
| CN116010016A (en) | Method, device, electronic equipment and medium for switching abnormal languages of service by system | |
| EP4033439A1 (en) | Commodity processing method and component, electronic device, and computer-readable medium | |
| CN111506285B (en) | Electronic price tag updating method and device, electronic equipment and readable medium | |
| CN109600722B (en) | Short message receiving verification method and device, electronic equipment and storage medium | |
| CN112766969A (en) | Mobile payment method and system, payment device and computer readable storage medium | |
| CN112948733A (en) | Interface maintenance method, device, computing equipment and medium | |
| CN111695985A (en) | System and method for processing voluntary deposit service of accumulation fund | |
| CN113448960A (en) | Method and device for importing form file | |
| US20230004435A1 (en) | Self-service platform integration | |
| CN113157382B (en) | Virtual drive-based equipment calling method and device | |
| CN112036898B (en) | Payment mode determining method and device, electronic equipment and storage medium | |
| CN113535101B (en) | Print file generation method and device, storage medium and electronic equipment | |
| EP4044091A1 (en) | Method and system for generating customized electronic checkout user interfaces |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information |
Address after: 201, room 518000, building A, No. 1, front Bay Road, Qianhai Shenzhen Guangdong Shenzhen Hong Kong cooperation zone (Qianhai business secretary) Applicant after: ONECONNECT FINANCIAL TECHNOLOGY Co.,Ltd. (SHANGHAI) Address before: 518000 Guangdong city of Shenzhen province Qianhai Shenzhen Hong Kong cooperation zone before Bay Road No. 1 building 201 room A Applicant before: ONECONNECT FINANCIAL TECHNOLOGY Co.,Ltd. (SHANGHAI) |
|
| CB02 | Change of applicant information | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |