WO2017181801A1

WO2017181801A1 - Hypertext transfer protocol request identification system and method

Info

Publication number: WO2017181801A1
Application number: PCT/CN2017/077408
Authority: WO
Inventors: 乐毅
Original assignee: 上海斐讯数据通信技术有限公司
Priority date: 2016-04-20
Filing date: 2017-03-21
Publication date: 2017-10-26
Also published as: CN105812481A

Abstract

The invention provides a hypertext transfer protocol (HTTP) request identification system and method. The system comprises an interconnected protocol request terminal and an access terminal. The protocol request terminal is used to transmit to the access terminal an HTTP request. The access terminal is used receive the HTTP request, and determine according to the HTTP request whether an identification pattern is satisfied, so as to implement identification of the HTTP request. In the technical solution, the access terminal is employed to identify a pattern, and determine on the basis of the received HTTP request whether the identification pattern is satisfied, so as to determine a response, resulting in a technical effect of reducing server loads.

Description

Hypertext transfer protocol request identification system and method

Technical field

The present invention relates to a hypertext transfer protocol request identification system and method.

Background technique

Nowadays, free wireless networks are available in public places such as shopping malls and hospitals. However, most of these free wireless networks need to be authenticated through portal authentication. There are many ways to initiate portal authentication, for example, by launching portal authentication through WeChat public account. You must first pay attention to the WeChat public account of the mall and hospital before you can initiate portal authentication and finally complete the connection of the free wireless network. WeChat public account has a certain advertising role, so WeChat is often used as a tool for public free wireless network portal authentication.

The portal authentication initiation tool, such as WeChat, is actually a hypertext transfer protocol request process, and is still a method for the browser to reply to the content authentication portal page for final authentication according to the request. In the above process, the access terminal has two hypertext transfer protocol request reply modes, and the first type: the access terminal hijacks the user's hypertext transfer protocol request, and replies with a temporary transfer error (referred to as "Http 302 error") information. And the resource locator (referred to as "URL") in the hypertext transfer protocol request is used as the network redirect address in the error message, and the browser will jump according to the network redirect address; the second type: The inbound hijacks the user's hypertext transfer protocol request, replies with the request success message with the redirect information, and embeds the Java server page (hereinafter referred to as "jsp") redirect code in the reply.

However, the above two methods have their own drawbacks. In the first way, since the access terminal hijacks the Hypertext Transfer Protocol request by listening to the 80 port of the Transmission Control Protocol (referred to as "TCP"), in fact, it is not only initiated. The authenticated tool will send a hypertext transfer protocol request, and the browser or other software on all access terminals will send a hypertext transfer protocol request, so the access end will reply to the temporary transfer error message before the authentication succeeds. The browser or other software will be redirected to the authentication page in a large amount, causing the load on the authentication server to be too high, and eventually the authentication server will not work properly. In the second way, the hypertext transfer protocol request initiated by other software can be effectively blocked, and the browser does not initiate too many hypertext transfer protocol requests after receiving the request success information, which solves the first problem. In a way due to a large number of hypertext transfer protocol requests The authentication server is overloaded. However, in the second mode, the redirect address is embedded in the reply message through the jsp redirect code. Due to the difference of the operating system of the access terminal, the jsp redirect code may be unresolvable, and finally the user is authenticated in the portal. I cannot jump to the authentication page.

The invention clarifies and processes the hypertext transfer protocol request for initiating the portal authentication, and the access end determines, according to the recognition style, whether the hypertext transfer protocol request belongs to the portal authentication initiation request, and according to the judgment result, selects to reply the Http 302 information or Http 200 information. Thereby achieving the effect of reducing the load on the authentication server.

Summary of the invention

In response to the above problems, the present invention provides a hypertext transfer protocol request identification system.

The technical solution provided by the present invention is as follows:

A hypertext transfer protocol request identification system includes: a protocol request end and an access end connected to each other,

The protocol requesting end is configured to send a hypertext transfer protocol request to the access terminal;

The access end is configured to receive the hypertext transfer protocol request, and determine whether the recognition pattern is satisfied according to the hypertext transfer protocol request, and implement the identification of the hypertext transfer protocol request.

Preferably, the access end includes: a request style preset module, a request receiving module, an identification module, and a reply module;

The request pattern preset module is configured to preset a recognition style of the hypertext transfer protocol request;

The request receiving module, and the protocol requesting end, the request receiving module is configured to receive a hypertext transfer protocol request sent by the protocol requesting end;

The identification module is respectively connected to the request pattern preset module and the request receiving module, and the identification module requests the recognition style based on the hypertext transfer protocol preset by the request style preset module, and the received hypertext transfer protocol Requesting to make a judgment, and judging by the judgment result, the control reply module performs a reply;

The reply module is respectively connected to the identification module and the protocol requesting end, and the replying module sends a reply message to the protocol requesting end based on the control of the identifying module.

Preferably, the hypertext transfer protocol request with the recognition pattern comprises: a resource locator and a target A character is recognized, and the identification character is located after the resource locator.

Preferably, the request pattern preset module comprises: an input selection unit, a style input unit, a combination unit, and a storage unit,

The input selection unit is configured to select an input type, the input type is an input identification character, or the input type is an input resource locator and an identification character.

The style input unit is connected to the input selection unit, the style input unit is configured to input a logo character, or the style input unit is configured to input a resource locator and a logo character;

The combining unit is connected to the style input unit, and the combining unit is configured to splicing the identifier character after the resource locator to form a hypertext transfer protocol request having a recognition style;

The storage unit is connected to the combination unit, and the storage unit is configured to store the identification pattern.

Preferably, the identification module includes: a style analysis unit connected to each other and an analysis result identification unit,

The pattern parsing unit is configured to parse the hypertext transfer protocol request according to the recognition style, and obtain an analysis result;

The analysis result identification unit is configured to determine the reply content according to the analysis result.

In view of the above problems, the present invention also provides a hypertext transfer protocol request identification method.

The technical solution provided by the present invention is as follows:

Presetting the hypertext transfer protocol request identification pattern for identification on the access end;

The access terminal receives the hypertext transfer protocol request;

The access end determines whether the hypertext transfer protocol request satisfies the recognition pattern;

Responding to a temporary transfer error message when the received hypertext transfer protocol request satisfies the recognition pattern;

When the received hypertext transfer protocol request does not satisfy the recognition pattern, the response success message including the network redirect address is replied.

Preferably, the preset hypertext transfer protocol request identification pattern for identification comprises:

Enter the identification character;

Splicing the identification character after the resource locator to form an identification pattern;

The recognition pattern is stored.

Enter the resource locator and the identification character;

The recognition pattern is stored.

Preferably, the determining whether the hypertext transfer protocol request satisfies the recognition style comprises:

Whether the identifier character can be obtained after the resource locator;

When the identifier character can be obtained, it indicates that the received hypertext transfer protocol request satisfies the recognition style;

When the identification character is not obtained, it indicates that the received Hypertext Transfer Protocol request does not satisfy the recognition pattern.

Whether the identifier character can be obtained after the resource locator;

When the identifier character can be obtained, it is determined whether the resource locator is the same as the resource locator in the recognition style;

When the same, it indicates that the received hypertext transfer protocol request satisfies the recognition pattern;

When the same, it indicates that the received Hypertext Transfer Protocol request does not satisfy the recognition pattern.

The hypertext transfer protocol request identification system and method provided by the present invention can bring the following beneficial effects:

In the present invention, the technical effect of reducing the load of the authentication server is obtained by the access end identifying whether the received hypertext transfer protocol request has an identification pattern and determining a technical solution for replying the content based on the recognition result.

In the present invention, by setting a technical solution of requesting a style preset module on the access end, the identification style can be set conveniently and quickly.

In the present invention, the identification character can be conveniently obtained by splicing the identification character to the resource locator as a technical solution of the hypertext transfer protocol request having the recognition pattern.

DRAWINGS

The above described features, technical features, advantages and implementations thereof will be further described in the following, in which the preferred embodiments are described in the <RTIgt;

1 is a detailed block diagram of a hypertext transfer protocol request identification system in the present invention;

2 is a diagram showing a specific embodiment of a hypertext transfer protocol request identification system according to the present invention;

3 is a flow chart of a method for identifying a hypertext transfer protocol request in the present invention.

Description of the reference numerals:

100-protocol requesting end, 200-access end, 201-requesting style presetting module, 202-requesting receiving module, 203-recognition module, 204-reply module, 20101-input selection unit, 20102-style input unit, 20103- Combination unit, 20104-storage unit, 20301-style parsing unit, 20302-analysis result identification unit.

detailed description

In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the specific embodiments of the present invention will be described below with reference to the accompanying drawings. Obviously, the drawings in the following description are only some embodiments of the present invention, and those skilled in the art can obtain other drawings according to the drawings without obtaining creative labor, and obtain Other embodiments.

FIG. 1 shows a hypertext transfer protocol request identification system provided by the present invention. As can be seen from the figure, in the hypertext transfer protocol request identification system, the interconnected protocol requester 100 and the access terminal 200 are included.

In a specific embodiment, various APP (Application) software in the mobile phone, a browser in the mobile phone, etc. can be used as the protocol requesting end 100, and they can send a hypertext transfer protocol request to the access terminal 200 (below Referred to as "Http request", and generally contains a resource locator (referred to as "URL") in the Http request sent, for example: http://www.123.com .

The access terminal 200 is generally a router or the like. The Http request sent by the protocol requesting end 100 enters the access terminal 200, and the request receiving module 202 in the access terminal 200 receives the Http request, where the request receiving module 202 performs no. Differential reception, that is, whether the Http request satisfies the recognition pattern, the reception is performed, and the Http request is transmitted to the identification module 203 in the access terminal 200, and the identification module 203 performs pattern recognition. The identification style of the Http request can be preset by the request style preset module 201 in the access terminal 200. The main function of the recognition style is to distinguish the category of the Http request, because the access terminal 200 responds with the Http 200 information with the redirect code. In response to the Http302 information with the redirected address, but if the Http 200 information is returned during the portal authentication, there is a possibility that the portal cannot be redirected. Therefore, the Http request initiated during the portal authentication may be identified, and the identification module 203 determines the received Whether the Http request satisfies the recognition style. If the recognition style is satisfied, it indicates that the received Http request may be used to initiate the portal authentication. At this time, replying the Http302 information with the redirected address can ensure the success of the jump portal, if the identification is not satisfied. The style indicates that the received Http request has nothing to do with the portal authentication. At this time, replying to the Http200 information with the redirect code can reduce the load of the portal authentication server. The reply module 204 in the access terminal 200 is configured to feed back the reply information to the protocol requesting end 100.

FIG. 2 shows a hypertext transfer protocol request identification system provided by the present invention. As can be seen from the figure, on the basis of FIG. 1, the request pattern preset module 201 includes an input selection unit 20101, a style input unit 20102, a combination unit 20103, and a storage unit 20104.

For the recognition style, we generally use a combination of URL and identification characters. In fact, the combined recognition style is also a URL, but it contains the URL address part, for example: http://www.123.com , and the identification character part, for example :abc. At this time, we can select to set only the identification characters or select the URL and the identification character content through the input selection unit 20101. After selection, the input can be made through the style input unit 20102, which is convenient and quick to set the recognition style. There are many combinations of URLs and logo characters. We use a convenient post-processing method as a combination method, that is, after the logo characters are spliced to the URL, for example: http://www.123.com? Ysgs, this process is completed by the combination unit 20103. After the combination is completed, the storage unit saves the combined Http request for acquisition by the identification module.

At the same time, on the basis of FIG. 1, the identification module 203 includes: a style parsing unit 20301 and an parsing result identifying unit 20302;

Since the Http request is received indiscriminately, the Http request must be parsed first. The style parsing unit 20301 parses the received Http request, for example, using the URL and the identifier character as the recognition style, and the style parsing unit 20301 needs to try to obtain the identifier character from the Http request. If the identifier character can be obtained, and the identifier character is the same as the identifier character in the recognition style, it can indicate that the Http request is a request initiated by the portal authentication or some Http request that needs to reply to the Http302 information with the redirected address; if not, or Even if the acquisition is not the same as the identification character in the recognition style, it means that the Http200 information with the redirect code can be replied for the purpose of reducing the server load.

FIG. 3 shows a hypertext transfer protocol request identification method provided by the present invention. Specifically, when the system needs to use the system to identify and reply to the Http request, the Http request recognition style is preset in the system, and the received Http request can be identified only after the recognition style is set in advance. We generally use a combination of URL and logo characters as the recognition style. In fact, the combined recognition style is also a URL, but it contains the URL address part, for example: http://www.123.com , and the identifier part, for example: Abc. At this point, we can choose to set only the identifier characters, that is, we do not limit the content of the URL address part, or we can choose to set the URL and the identifier character content, that is, the Http request sent by the protocol requester must fully satisfy the setting. The content will respond accordingly. Below we explain the two situations in detail:

When only the logo characters are set, you can enter the logo characters such as bszf. There are many combinations of URLs and logo characters. Let's take the example of splicing the logo characters to the URL. In this case, the recognition style is: “?bszf” This recognition style does not restrict the content of the URL address part. When receiving an Http request, it is preferred to determine whether the identifier character is included, for example: http://www.123.com , which does not contain the "bszf" identifier character, for example: http://www.456.com? Bszf , which contains the identifier character "bszf", also for example: http://www.789.com? Bszf also contains the identifier character "bszf". Since only the logo characters are set, we do not compare the URL address parts of the last two examples, namely http://www.456.com and http://www.789.com , only the logo character part. Comparison. In summary, it can be seen that the first example does not include the identification character "bszf", and the latter two examples have the same identification character "bszf" as the identification character in the recognition style, and thus can be judged, the first example The Http request may not be a request for portal authentication or a request to reply to the Http302 information with the redirected address. In this case, the Http200 information with the redirect code may be replied to reduce the server load; the latter two Http requests may be It is a request for portal authentication or a request to reply to the Http302 information with a redirected address. In this case, the Http302 information with the redirected address needs to be replied to ensure that the protocol requester can obtain the redirected address.

When the URL and the identification character content are set, you can enter the URL, for example: http://www.123.com and the identification character, for example: bszf. There are many combinations of URLs and logo characters. Let's take the example of splicing the logo characters to the URL. In this case, the recognition style is: " http://www.456.com?bszf ". When receiving an Http request, it is preferred to determine whether the identifier character is included, for example: http://www.123.com , which does not contain the "bszf" identifier character, for example: http://www.456.com? Bszf , which contains the identifier character "bszf", also for example: http://www.789.com? Bszf also contains the identifier character "bszf". Since the URL and the character of the identification character are set, we compare the URL address part and the identification character in the three examples. In summary, it can be seen that the first example does not include the identification character "bszf". The latter two examples have the same identification character "bszf" as the identification character in the recognition style, but the URL address portion and the identification URL in the identification example in the third example. Partially different, it can be judged that the first and third cases of the Http request may not be a request for portal authentication or a request to reply to the Http 302 information with a redirected address, and only need to reduce the burden on the server. Respond to the Http 200 information with the redirect code; the second instance of the Http request may be a request for portal authentication or a request to reply to the Http 302 information with the redirected address, in which case the Http 302 with the redirected address needs to be replied To ensure that the requesting end of the protocol can obtain the redirected address.

In summary, we take the example of logging into the free public wireless network through WeChat public account authentication. First of all, we can set the identification character on the access side, for example: set with WeChat ID number, the content is "weixinID=123", because we can format many Http requests, it is easy to have Http request with the same identification character. So we can further set up the URL address part of the Http request, here for example: http://www.mhrz.com , then the whole recognition style is http://www.mhrz.com? weixinID=123 . We generally use the WeChat public number developer platform to create a public number custom menu, and a portal to authenticate the portal. The URL address that triggers the portal authentication is set in the button. Since the portal authentication request needs to reply to the Http302 information, the setting Http request must satisfy the identification style set on the access end, and must be set to http://www.mhrz. Com? weixinID=123, the access end can reply to the Http302 information. When the user needs to connect to the wireless network, the user can send an Http request containing the above URL to the access terminal by clicking the button, and the access terminal intercepts the Http request, first obtains the identifier character weixinID=123, and then http://www.mhrz. Com judges that the condition is met, and the access end replies with the Http302 information with the redirected address.

It should be noted that the above embodiments can be freely combined as needed. The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It should be considered as the scope of protection of the present invention.

Claims

A hypertext transfer protocol request identification system, characterized in that the hypertext transfer protocol request identification system comprises: a protocol request end and an access end connected to each other,

The protocol requesting end is configured to send a hypertext transfer protocol request to the access terminal;

The access end is configured to receive the hypertext transfer protocol request, and determine whether the recognition pattern is satisfied according to the hypertext transfer protocol request, and implement the identification of the hypertext transfer protocol request.
The hypertext transfer protocol request identification system according to claim 1, wherein the access terminal comprises: a request style preset module, a request receiving module, an identification module, and a reply module;

The request pattern preset module is configured to preset a recognition style of the hypertext transfer protocol request;

The request receiving module, and the protocol requesting end, the request receiving module is configured to receive a hypertext transfer protocol request sent by the protocol requesting end;

The identification module is respectively connected to the request pattern preset module and the request receiving module, and the identification module requests the recognition style based on the hypertext transfer protocol preset by the request style preset module, and the received hypertext transfer protocol Requesting to make a judgment, and judging by the judgment result, the control reply module performs a reply;

The reply module is respectively connected to the identification module and the protocol requesting end, and the replying module sends a reply message to the protocol requesting end based on the control of the identifying module.
The hypertext transfer protocol request identification system according to any one of claims 1 to 2, wherein the hypertext transfer protocol request having the identification pattern comprises: a resource locator and an identification character, and the identification character is located After the resource locator.
The hypertext transfer protocol request identification system according to claim 3, wherein the request pattern preset module comprises: an input selection unit, a style input unit, a combination unit, and a storage unit,

The input selection unit is configured to select an input type, where the input type is an input identification character, or the input type is an input resource locator and an identifier character;

The style input unit is connected to the input selection unit, the style input unit is configured to input a logo character, or the style input unit is configured to input a resource locator and a logo character;

The combining unit is connected to the style input unit, and the combining unit is configured to Forming a hypertext transfer protocol request with an identification pattern after the character is spliced to the resource locator;

The storage unit is connected to the combination unit, and the storage unit is configured to store the identification pattern.
The hypertext transfer protocol request identification system according to claim 3, wherein the identification module comprises: an interconnected style parsing unit and an parsing result identifying unit,

The pattern parsing unit is configured to parse the hypertext transfer protocol request according to the recognition style, and obtain an analysis result;

The analysis result identification unit is configured to determine the reply content according to the analysis result.
A hypertext transfer protocol request identification method, wherein the hypertext transfer protocol request identification method comprises:

Presetting the hypertext transfer protocol request identification pattern for identification on the access end;

The access terminal receives the hypertext transfer protocol request;

The access end determines whether the hypertext transfer protocol request satisfies the recognition pattern;

Responding to a temporary transfer error message when the received hypertext transfer protocol request satisfies the recognition pattern;

When the received hypertext transfer protocol request does not satisfy the recognition pattern, the response success message including the network redirect address is replied.
The Hypertext Transfer Protocol request identification method according to claim 6, wherein the preset hypertext transfer protocol request identification pattern for identification comprises:

Enter the identification character;

Using the identification character as an identification style;

The recognition pattern is stored.
The Hypertext Transfer Protocol request identification method according to claim 6, wherein the preset hypertext transfer protocol request identification pattern for identification comprises:

Enter the resource locator and the identification character;

Splicing the identification character after the resource locator to form an identification pattern;

The recognition pattern is stored.
The hypertext transfer protocol request identification method according to claim 7, wherein the determining whether the hypertext transfer protocol request satisfies the recognition style comprises:

Whether the identifier character can be obtained after the resource locator;

When the identifier character can be obtained, it indicates that the received hypertext transfer protocol request satisfies the recognition style;

When the identification character is not obtained, it indicates that the received Hypertext Transfer Protocol request does not satisfy the recognition pattern.
The hypertext transfer protocol request identification method according to claim 8, wherein the determining whether the hypertext transfer protocol request satisfies the recognition style comprises:

Whether the identifier character can be obtained after the resource locator;

When the identification character is not obtained, it indicates that the received Hypertext Transfer Protocol request does not satisfy the recognition pattern.

When the identifier character can be obtained, it is determined whether the resource locator is the same as the resource locator in the recognition style;

When the same, it indicates that the received hypertext transfer protocol request satisfies the recognition pattern;

When the same, it indicates that the received Hypertext Transfer Protocol request does not satisfy the recognition pattern.