CN103618696A - Method and server for processing cookie information - Google Patents
Method and server for processing cookie information Download PDFInfo
- Publication number
- CN103618696A CN103618696A CN201310551633.7A CN201310551633A CN103618696A CN 103618696 A CN103618696 A CN 103618696A CN 201310551633 A CN201310551633 A CN 201310551633A CN 103618696 A CN103618696 A CN 103618696A
- Authority
- CN
- China
- Prior art keywords
- cookie
- cross
- site
- list
- website
- 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
- 235000014510 cooky Nutrition 0.000 title claims abstract description 578
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000012545 processing Methods 0.000 title claims abstract description 20
- 238000013515 script Methods 0.000 claims description 39
- 230000006399 behavior Effects 0.000 abstract description 36
- 238000010586 diagram Methods 0.000 description 8
- 238000012790 confirmation Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 4
- 238000012216 screening Methods 0.000 description 3
- GOLXNESZZPUPJE-UHFFFAOYSA-N spiromesifen Chemical compound CC1=CC(C)=CC(C)=C1C(C(O1)=O)=C(OC(=O)CC(C)(C)C)C11CCCC1 GOLXNESZZPUPJE-UHFFFAOYSA-N 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 206010012601 diabetes mellitus Diseases 0.000 description 2
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- PCHJSUWPFVWCPO-UHFFFAOYSA-N gold Chemical compound [Au] PCHJSUWPFVWCPO-UHFFFAOYSA-N 0.000 description 1
- 239000010931 gold Substances 0.000 description 1
- 229910052737 gold Inorganic materials 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000001012 protector Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method and server for processing cookie information. According to the embodiment, the method includes the steps that cookies uploaded by all browser sides are collected; cross-station cookies tracking user behaviors are determined according to the cookies; a cookie list of the cross-website cookies and/or a website list of websites to which the cross-website cookies belong are generated according to the cross-website cookies; the cookie list and/or the website list are/is distributed to all the browser sides.
Description
Technical Field
The invention relates to the technical field of computer networks, in particular to a method and a server for processing cookie information.
Background
Since the birth of Cookie in 1993, the Cookie has the special principle that the A website stores the user information in the Cookie, and the B website has no right to directly acquire the user information. However, the code of some third party advertising unions is now widely used. Therefore, the user searches a keyword in the site a, and the user continues to visit the site B, and since the site B also uses a third-party advertisement code of the same family, the code can acquire the search behavior of the user in the site a from the Cookie, and further display more accurate advertisement (such as hundred degree "winning advertisement", "enterprise alliance", and "hong medias"). For example, a user searches a federation website for keywords such as "diabetes" and visits its federation website, with an immediate diabetes treatment advertisement appearing on the page. This is a suspicion of privacy violation, if not reported in advance, with the user's consent. The cross-site Cookie is just the chief culprit of divulging user privacy, so that the problem that a website is limited to use the cross-site Cookie and a user is provided with a function option of forbidding tracking (DNT) is urgent.
In order to avoid the use of the cross-site Cookie, the method used by the existing browser (such as a chrome browser) is as follows: and when the A website is accessed, the cookie of the third-party website (such as the B website) is prohibited from being saved.
However, if the saving of cookies of all third-party websites is prohibited according to the conventional method, the saving of cookies of the third-party websites is actually needed at some time, for example, the saving of cookies of some third-party websites is needed to carry out information transfer when jumping among websites. The prior proposal influences the performance of the network, leads to the running of the network to be not smooth enough,
disclosure of Invention
In view of the above, the present invention has been made to provide a method of processing cookie information and a corresponding server that overcome or at least partially solve the above problems.
According to an aspect of the present invention, an embodiment of the present invention provides a method for processing cookie information, including:
collecting cookies uploaded by each browser side; determining cross-site cookies tracking user behaviors according to the cookies; generating a cookie list of the cross-site cookie and/or a website list of a website to which the cross-site cookie belongs according to the cross-site cookie; and distributing the cookie list and/or the website list to each browser side.
Optionally, the collecting cookies uploaded by each browser side includes:
collecting basic information of the cookie uploaded on each browser side, wherein the basic information comprises a main key, creation time, a host where the cookie is located, a name, a value and expiration time; and the number of the first and second groups,
collecting cross-site information of cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises the following steps: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
Optionally, the determining a cross-site cookie for tracking user behavior according to the cookie includes:
determining the cookie uploaded by the browser side as a cross-site cookie; or determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored.
Optionally, the determining the cross-site cookie according to the storage frequency of the uploaded cookie and/or the number of websites visited by the browser when the cookie is stored includes:
when the storage times of the uploaded cookies on the browser side exceed a time threshold value, determining the cookies as cross-site cookies; and/or determining the cookie as a cross-site cookie when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored.
Optionally, the generating a cookie list of the cross-site cookie and/or a website list of a website to which the cross-site cookie belongs according to the cross-site cookie includes:
generating a cookie database table according to the determined basic information of the cross-site cookie, generating a cross-domain database table according to the determined cross-site information of the cross-site cookie, and forming a cookie list by the cookie database table and the cross-domain database table; and/or generating a website list according to JS scripts for executing cross-site cookie writing operation or url of HTTP return headers in the form of iframe.
Optionally, the generating the website list according to the JS script that performs the cross-site cookie writing operation or the url of the HTTP return header in the form of the iframe includes:
and acquiring the number of different websites visited by the browser when the same cookie is stored, and arranging urls of HTTP return headers in JS scripts or iframe forms in a sequence from high to low according to the number to obtain a website list.
According to another aspect of the present invention, an embodiment of the present invention provides a server, including:
the collecting unit is suitable for collecting the cookies uploaded by each browser side; a cross-site cookie determining unit, which is suitable for determining a cross-site cookie tracking the user behavior according to the cookie; the list generating unit is suitable for generating a cookie list of the cross-site cookies and/or a website list of websites to which the cross-site cookies belong according to the cross-site cookies; and the list issuing unit is suitable for distributing the cookie list and/or the website list to each browser side.
Optionally, the collecting unit is adapted to collect basic information of the cookie uploaded on each browser side, where the basic information includes a primary key, creation time, host where the cookie is located, name, value, and expiration time; and collecting cross-site information of the cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
Optionally, the cross-site cookie determining unit is adapted to determine a cookie uploaded by the browser side as a cross-site cookie; or determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored.
Optionally, the cross-site cookie determining unit is adapted to determine the uploaded cookie as a cross-site cookie when the number of times the cookie is stored on the browser side exceeds a number threshold; and/or determining the cookie as a cross-site cookie when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored.
Optionally, the list generating unit is adapted to generate a cookie database table according to the basic information of the determined cross-site cookie, and generate a cross-domain database table according to the cross-site information of the determined cross-site cookie, where the cookie database table and the cross-domain database table form a cookie list; and/or generating a website list according to JS scripts for executing cross-site cookie writing operation or url of HTTP return headers in the form of iframe.
Optionally, the list generating unit is adapted to obtain the number of different websites visited by the browser when the same cookie is stored, and arrange urls of the JS script or the HTTP return header in the iframe form in order of the number from high to low to obtain the website list.
The embodiment of the invention can acquire the cookie of the website for tracking the user behavior by collecting the cookie of each browser side and determining the technical means of cross-site cookie tracking the user behavior; by means of the technical means that the cookie lists and/or the website lists are generated according to the cross-site cookies and issued to the browser sides, the browser sides can acquire the cross-site cookies, so that the browser sides can only forbid storage of cookie information of third-party websites for user behavior tracking, the problems that in the prior art, storage of cookies of all third-party websites is forbidden, network performance is poor, and network operation is not smooth enough are solved, safety of user privacy data can be improved, and network performance and smoothness of network operation are guaranteed.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 illustrates a flow diagram of a method of processing cookie information in accordance with one embodiment of the invention;
FIG. 2 is a flowchart illustrating a method for using a cookie list in a method of processing cookie information according to another embodiment of the present invention;
FIG. 3 illustrates a flow diagram of a cross-site cookie determination method of processing cookie information in a method according to yet another embodiment of the invention;
FIG. 4 shows a schematic diagram of a display interface according to yet another embodiment of the invention;
FIG. 5 illustrates a flowchart of a method of processing cookie information according to yet another embodiment of the invention;
FIG. 6 is a diagram illustrating a browser architecture according to yet another embodiment of the present invention;
fig. 7 is a schematic diagram showing the structure of the acquisition unit in the browser shown in fig. 6;
fig. 8 shows a schematic diagram of a server architecture according to yet another embodiment of the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
One scenario in which the present invention may be applied may be: embedding a third-party advertisement page (B website page) in the a webpage in the form of iframe or including the third-party advertisement page in the form of JS (javascript) script, when the browser accesses the a webpage, saving a Cookie of the a website and a Cookie of the B website in the browser side, and when the user clicks the B website page embedded therein (or executes the JS script therein most directly when loading the b.com webpage), writing such an item in the Cookie of the B website locally recorded by the browser side through the JS code in the B website (i.e. the JS script): arrive = a website (this is plain text, actually this item written in the form of cipher text, the meaning of which is unknown to the other parties of the browser). Therefore, when the user accesses the B website, the cookie of the B website in the local area is read, and the user is informed that the A website is accessed, for example, the A website is a website for selling shoes, so that the information related to the shoes which come from the gold is loaded in the B website, and the fixed-point delivery of the advertisement information is realized.
The technical idea of the invention is mainly to distinguish the cookies of the third-party website, judge the cookies of the most suspicious third-party website tracking the user behavior through the browser, and prohibit the operations of reading and writing of the cross-site cookies and the like at the browser side.
An embodiment of the present invention provides a method for processing cookie information, referring to fig. 1, including the following steps:
s100: and acquiring a cookie list of cross-site cookies for tracking user behaviors and/or a website list of websites to which the cross-site cookies belong at the browser side.
In the step, the cross-site cookies monitored by the browser side are uploaded to the cloud server side so as to generate a cookie list and/or a website list on the cloud server side, and then the cookie list and/or the website list issued by the cloud server side are received.
S102: and confirming that the cookie information requested in the access request received by the browser side hits the cookie list and/or the website list.
In this step, when the requested cookie information is recorded in at least one of the cookie list and the website list, it is confirmed that the cookie list and/or the website list is hit, and the requested cookie is a cross-site cookie, and the process proceeds to step S104, otherwise, the requested cookie is not a cross-site cookie, and the operation on the cookie is permitted.
S104: the access request is denied operation on the requested cookie information at the browser side.
In the step, the access request is refused to carry out reading and writing operations and the like on the cross-site cookie at the browser side.
The embodiment of the invention can acquire the cookie of the website tracking the user behavior by the technical means of acquiring the cookie list of the cross-site cookie and/or the website list of the website to which the cross-site cookie belongs; by the technical means of confirming that the cookie information requested by the browser side hits the cookie list and/or the website list and refusing the operation of the requested cookie information, the cookie information of the third-party website for tracking the user behavior can be only prohibited from being stored, so that the problems of poor network performance and unsmooth network operation caused by prohibition of storage of cookies of all third-party websites in the prior art are solved, the safety of user privacy data can be improved, and the network performance and the smoothness of network operation are ensured.
Another embodiment of the present invention is mainly described in terms of a cookie list of a cross-site cookie and/or a method for using a website list of a website to which the cross-site cookie belongs in a method for processing cookie information, and other contents refer to other embodiments of the present invention. Referring to fig. 2, there is shown a flow chart of a method for using a cookie list in a method for processing cookie information, comprising the following steps:
s200: the browser is started.
S202: and acquiring a cookie list of the tracking user from the cloud server side.
The cookie list records various information of the cross-site cookies. The cookie list may include a cookie database table and a Cross domain database table.
Referring to table 1 below, the cookie database table includes the following basic information for cookies: primary key, creation time, host where cookie is located (host), name, value, and expiration time.
Table 1cookie database table
| Id | Primary key for Cross _ domain indexing |
| Creation_utc | Creation time |
| Host_key | Host of Cookie |
| Name | Name (R) |
| Value | Value of |
| Expired_utc | Expiration time |
| …… | Other items |
Referring to table 2 below, the Cross-domain database table includes the following Cross-site information for the Cross-site cookie: a url (uniform resource locator) of an HTTP return header in the form of a JS script or iframe, a main frame url of a website accessed by the browser side when storage is performed on the suspect cookie, a main key, a creation time, and a last access time.
Table 2 cross-domain database table
| Trace_url | Url of Iframe Return header or url of JS script |
| Host_url | Url of main frame |
| Cookie_id | Primary key in Cookie database table |
| Creation_utc | Creation time |
| Last_access_utc | Last access time |
Optionally, in this step, a website list of websites to which cookies of the tracking user belong may also be simultaneously obtained from the cloud server side. The url of the Iframe return header or the url of the JS script is recorded in the website list.
S204: the web or browser user initiates an HTTP (HyperText Transfer Protocol) request that carries a cookie (e.g., timestamp, etc.) associated with the current host.
S206: and acquiring all cookie data belonging to the current host from the cookie list, such as the cookie database table belonging to the current host and the cross-domain database table belonging to the current host.
S208: it is determined whether the cookie to be sent has a cross-site record in the cross-domain database table.
That is, it is determined whether a cookie requested by the HTTP request has a cross-site record in the cross-domain database table of the current host, and if so, it is determined whether the cross-site record exists by querying whether a primary key (Id) of the requested cookie is recorded in the cross-domain database table, if so, S210 is entered, otherwise, S214 is entered.
From the Id value, it is known whether a cookie is stored in iframe form (or due to JS scripts), and if so, it is likely to be a cross-site cookie.
S210: and judging whether the recorded items hit the black cookie list or not.
The black cookie list is a cookie database table under the current host, and whether the cookie is recorded in the cookie database table under the current host is inquired in the cross-domain database table, if so, the step S212 is performed, and if not, the step S214 is performed.
S212: suspect cookies are filtered.
In this case, it is determined that the cookie requested to be sent is a cross-site cookie for tracking user behavior, and the read/write operation on the cookie is rejected or the cookie is directly deleted, and the process proceeds to S216.
S214: the cookie is handed over to the HTTP return header, which initiates the HTTP request.
In this case, it is determined that the requested cookie is not a cross-site cookie that tracks user behavior, and the cookie is set in an HTTP return header and sent to the web page or the user by the HTTP request.
S216: directly initiating an HTTP request that does not include the requested cookie.
The above flow mainly describes the matching flow of the requested cookie based on the cookie list, and when the requested cookie is processed by using the website list, the browser side intercepts the cross-site cookie read-write operation of all websites recorded in the website list, for example, when the URL of the access request is confirmed to be recorded in the website list, it is confirmed that the cookie information requested in the access request hits the website list, and the read-write operation of the cookie by the browser side is not executed.
The embodiment of the invention can acquire the cookie of the website tracking the user behavior by the technical means of acquiring the cookie list of the cross-site cookie and/or the website list of the website to which the cross-site cookie belongs; by the technical means of confirming that the cookie information requested by the browser side hits the cookie list and/or the website list and refusing the operation of the requested cookie information, the cookie information of the third-party website for tracking the user behavior can be only prohibited from being stored, so that the problems of poor network performance and unsmooth network operation caused by prohibition of storage of cookies of all third-party websites in the prior art are solved, the safety of user privacy data can be improved, and the network performance and the smoothness of network operation are ensured.
In the method for processing cookie information according to another embodiment of the present invention, a method for determining a cross-site cookie is described, and other contents are described in other embodiments of the present invention. Referring to fig. 3, the method comprises the following steps:
s300: the browser side has a write operation of the cross-site cookie.
When the browser accesses the first website, it is monitored that the browser side executes the writing operation of the cookie of the second website. For example, when the browser accesses an a.com site, the browser side writes a data item of arrive: a.com in a cookie of the b.com site.
S302: and judging whether the writing operation is executed by a JS script embedded in the first website or an HTTP return header of the first website in an iframe form, if so, entering S304, and if not, entering S306.
S304: confirming that the cookie is a suspicious cookie, storing the suspicious cookie and a first website accessed by the browser side when the suspicious cookie is stored. Namely, when the cookie is stored, the host of the main frame, namely the current page, is stored in the cross-domain database table at the same time.
Com, and a.com is also recorded in correspondence with this data item, so that it is known that the a.com is recorded at the time of access to a.com: com this cookie data item.
Optionally, the operation of determining the suspicious cookie in this step may also adopt the following method:
when the browser accesses the first website, it is monitored that the cookie of the second website is written by a JS script embedded in the first website or an HTTP return header of the first website in an iframe form on the browser side, and when the browser accesses the second website, the same writing operation is not executed on the browser side, and the cookie is confirmed to be a suspicious cookie. For example, when the browser accesses a.com, a cookie of b.com is stored on the browser side: com, while the browser alone does not generate such a cookie, it is very likely that this cookie is a cookie to track user behavior from both aspects.
S306: the cookie is stored. In this case, it is determined that the cookie is not a suspected cookie for tracking user behavior, and the cookie is stored directly.
S308: when the storage times of the suspicious cookie exceed a threshold value (for example, 5 times), the suspicious cookie is confirmed to be a cross-site cookie, and the cross-site cookie and a first website accessed by the browser side when the cross-site cookie is stored are uploaded to the cloud server side.
If the iframe of b.com is inserted into various websites, such as the c.com website, the d.com website, and the e.com website, suspicious cookies of various websites are recorded in b.com cookies local to the browser. The browser side thus knows the information: the cookie of the b.com site is written when accessing the a.com site, the c.com site, the d.com site, and the e.com site. When the storage times of the suspicious cookie are larger than a threshold value, the cookie is likely to be a cross-site cookie tracking user behaviors, the cross-site cookie is reported to the cloud, and the cookie is listed in a blacklist (namely, a cookie database table) by a cloud background.
S310: the user checks for cross-site cookies from the browser-specific portal.
After the suspicious cookie is obtained in step S304, the cookie data is converted into a format that can be recognized by the user and displayed, and the same processing may be performed on the non-suspicious cookie. The cookie information is provided to the user through a dedicated entry (display interface) of the browser. Referring to fig. 4, a schematic diagram of a display interface according to an embodiment of the present invention is provided. The display interface displays the related information of the cross-site cookie under the item of cross-site tracking log, such as a third-party website for cross-site tracking, an embedded tracking code file, the number of cross-site tracking and the like.
The display interface can be provided by a name, such as a browser subprocess of a website privacy protector, displays the acquired cookie list and/or the acquired website list on the display interface, receives a cookie operation instruction sent by a browser user through the display interface, and executes corresponding operation on cookie information on the browser side.
The embodiment of the invention can acquire the cookie of the website tracking the user behavior by the technical means of acquiring the cookie list of the cross-site cookie and/or the website list of the website to which the cross-site cookie belongs; by the technical means of confirming that the cookie information requested by the browser side hits the cookie list and/or the website list and refusing the operation of the requested cookie information, the cookie information of the third-party website for tracking the user behavior can be only prohibited from being stored, so that the problems of poor network performance and unsmooth network operation caused by prohibition of storage of cookies of all third-party websites in the prior art are solved, the safety of user privacy data can be improved, and the network performance and the smoothness of network operation are ensured.
A method for processing cookie information according to another embodiment of the present invention may be executed by a cloud server, and referring to fig. 5, the method includes the following steps:
s500: and collecting the cookies uploaded on each browser side.
Optionally, collecting basic information of the cookie uploaded by each browser side, see table 1 above, where the basic information includes a primary key, creation time, host where the cookie is located, name, value, and expiration time;
and the number of the first and second groups,
collecting the cross-site information of the cookie uploaded by each browser side, referring to table 2 above, the cross-site information of the cookie includes: url of HTTP return header in the form of JS script or iframe, home frame url of website accessed by browser side when storing the cookie, home key, creation time, and last access time.
S502: determining a cross-site cookie for tracking user behavior according to the cookie, wherein the method comprises the following two ways:
the first mode is as follows: and determining the cookie uploaded by the browser side as the cross-site cookie, and screening the cross-site cookie only on the browser side in such a way so as to reduce the pressure of cloud processing.
The method for screening the cross-site cookies on the browser side comprises the following steps: when the browser accesses the first website, monitoring that the browser side executes the writing operation of the cookie of the second website; judging whether write operation is executed by a JS script embedded in a first website or a hypertext transfer protocol (HTTP) return header of the first website in an iframe form, if so, confirming that the cookie is a suspicious cookie, and storing the suspicious cookie and the first website accessed by a browser side when the suspicious cookie is stored; if not, storing the cookie; when the storage times of the suspicious cookie exceed a threshold value, the suspicious cookie is determined to be a cross-site cookie, and the cross-site cookie and a first website accessed by a browser side when the cross-site cookie is stored are uploaded to a cloud server side.
The method for confirming that the cookie is a suspicious cookie may further include: when the browser accesses the first website, it is monitored that the cookie of the second website is written by a JS script embedded in the first website or an HTTP return header of the first website in an iframe form on the browser side, and when the browser accesses the second website and the same writing operation is not performed on the browser side, the cookie is confirmed to be a suspicious cookie.
The second mode is as follows: and determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored. In this way, the cloud server analyzes cookie data reported by different browsers, and filters cross-site cookies at both the browser side and the server side, so as to improve the accuracy of the filtered cross-site cookies.
In a second mode, when the storage frequency of the uploaded cookie on the browser side exceeds a frequency threshold value, the cookie is determined to be a cross-site cookie; and/or determining the cookie as a cross-site cookie when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored.
S504: and generating a cookie list of the cross-site cookie and/or a website list of websites to which the cross-site cookie belongs according to the cross-site cookie.
Optionally, the cookie list includes a cookie database table and a cross-domain database table. And generating a cookie database table according to the basic information of the determined cross-site cookie, and generating a cross-domain database table according to the cross-site information of the determined cross-site cookie.
When the website list is generated, the website list is generated according to JS script for executing cross-site cookie write operation or url of HTTP return header in iframe form. Specifically, the number of different websites visited by the browser when the same cookie is stored is obtained, and urls of the JS script or HTTP return header in the iframe form are arranged in the order of the number from high to low, so that a website list is obtained.
S506: and distributing the cookie list and/or the website list to each browser side.
The cloud server issues the cookie list and/or the website list to the browser side, so that the browser side reads and writes the cross-site cookies by using the cookie list and/or the website list, and tracking of user behaviors is prevented.
The embodiment of the invention can acquire the cookie of the website for tracking the user behavior by collecting the cookie of each browser side and determining the technical means of cross-site cookie tracking the user behavior; by means of the technical means that the cookie lists and/or the website lists are generated according to the cross-site cookies and issued to the browser sides, the browser sides can acquire the cross-site cookies, so that the browser sides can only forbid storage of cookie information of third-party websites for user behavior tracking, the problems that in the prior art, storage of cookies of all third-party websites is forbidden, network performance is poor, and network operation is not smooth enough are solved, safety of user privacy data can be improved, and network performance and smoothness of network operation are guaranteed.
Yet another embodiment of the present invention provides a browser 600, and referring to fig. 6, the browser 600 includes:
the acquiring unit 610 is adapted to acquire a cookie list of a cross-site cookie tracking user behavior and/or a website list of a website to which the cross-site cookie belongs from a browser side; a hit confirmation unit 612 adapted to confirm that cookie information requested in the access request received at the browser side hits the cookie list and/or the website list; a rejecting unit 614 adapted to reject the access request to operate on the requested cookie information at the browser side.
Alternatively, referring to fig. 7, a schematic structural diagram of the acquisition unit is shown. The acquisition unit 610 includes an uploading subunit 6100 and a receiving subunit 6102. The uploading subunit 6100 is adapted to upload the cross-site cookies monitored by the browser side to the cloud server side, so as to generate a cookie list and/or a website list at the cloud server side; the receiving sub-unit 6102 is adapted to receive a cookie list and/or a website list issued by the cloud server.
Optionally, the obtaining unit 610 further includes a cross-site cookie validation subunit 6104 and a storage subunit 6106. The cross-site cookie confirmation subunit 6104 is adapted to monitor that the browser side executes the writing operation of the cookie of the second website when the browser accesses the first website; judging whether write operation is executed by a JS script embedded in the first website or a hypertext transfer protocol (HTTP) return header of the first website in the form of iframe, if so, confirming that the cookie is a suspicious cookie, and triggering a storage subunit 6106 to store the suspicious cookie and the first website accessed by the browser side when the suspicious cookie is stored; if not, triggering the storage subunit to store the cookie; when the storage times of the suspicious cookies exceed a threshold value, confirming that the suspicious cookies are cross-site cookies; a storage subunit 6106 adapted to store the suspect cookie and the first website accessed by the browser side when storing the suspect cookie, or store the cookie. The uploading subunit 6100 is further adapted to upload the cross-site cookie and the first website accessed by the browser side when storing the cross-site cookie to the cloud server side.
Optionally, the cross-site cookie confirmation subunit 6104 is further adapted to monitor that, when the browser accesses the first website, the write operation of the cookie of the second website is performed on the browser side by the JS script embedded in the first website or the HTTP return header in the form of iframe of the first website, and when the browser accesses the second website, the cookie is confirmed to be a suspicious cookie when the same write operation is not performed on the browser side.
Optionally, a storage subunit 6106, adapted to store the following basic information of the suspicious cookie: primary key, creation time, host where cookie is located, name, value and expiration time; and storing the cross-site information of the suspicious cookie as follows: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storage of the suspect cookie is performed, a home key, a creation time, and a last access time.
Optionally, the cookie list includes a cookie database table and a cross-domain database table, where the cookie database table includes basic information of the cross-site cookie, and the cross-domain database table includes cross-site information of the cross-site cookie; a hit confirmation unit 612, adapted to determine whether the requested cookie has a cross-site record in a cross-domain database table, and if so, determine whether the requested cookie is recorded in a cookie database table, if so, confirm a hit cookie list, otherwise, confirm a miss cookie list; if no cross-site record exists, confirming that the cookie list is not hit.
Optionally, the hit confirmation unit 612 is adapted to confirm that the URL of the access request is recorded in the website list, and then confirm that the cookie information requested in the access request hits the website list.
Optionally, the browser 600 further includes a display operation unit 616, adapted to display the acquired cookie list and/or website list on a display interface on the browser side; and receiving a cookie operation instruction sent by a browser user through a display interface, and executing corresponding operation on cookie information at the browser side.
The specific working modes of the units in the device embodiment of the invention can be seen in the corresponding method embodiment of the invention.
The embodiment of the invention can acquire the cookie of the website tracking the user behavior by the technical means of acquiring the cookie list of the cross-site cookie and/or the website list of the website to which the cross-site cookie belongs; by the technical means of confirming that the cookie information requested by the browser side hits the cookie list and/or the website list and refusing the operation of the requested cookie information, the cookie information of the third-party website for tracking the user behavior can be only prohibited from being stored, so that the problems of poor network performance and unsmooth network operation caused by prohibition of storage of cookies of all third-party websites in the prior art are solved, the safety of user privacy data can be improved, and the network performance and the smoothness of network operation are ensured.
Another embodiment of the present invention provides a server 800, where the server 800 may be disposed in a cloud and implemented by a cloud server, referring to fig. 8, and the server 800 specifically includes:
a collecting unit 810 adapted to collect cookies uploaded by each browser side; a cross-site cookie determination unit 812 adapted to determine a cross-site cookie tracking user behavior from the cookie; a list generating unit 814, adapted to generate a cookie list of the cross-site cookie and/or a website list of websites to which the cross-site cookie belongs according to the cross-site cookie; a list issuing unit 816, adapted to distribute the cookie list and/or the website list to each browser side.
Optionally, the collecting unit 810 is adapted to collect basic information of the cookie uploaded on each browser side, where the basic information includes a primary key, a creation time, a host where the cookie is located, a name, a value, and an expiration time; and collecting cross-site information of the cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
Optionally, in an alternative manner, the cross-site cookie determining unit 812 is adapted to determine the cookie uploaded on the browser side as the cross-site cookie. In this way, the cross-site cookie screening is only carried out on the browser side, so that the cloud processing pressure is reduced. Or, in another mode, the cross-site cookie determination unit 812 determines the cross-site cookie according to the number of times the uploaded cookie is stored on the browser side and/or the number of websites visited by the browser when the cookie is stored. In this way, the cloud server analyzes cookie data reported by different browsers, and filters cross-site cookies at both the browser side and the server side, so as to improve the accuracy of the filtered cross-site cookies.
Optionally, the cross-site cookie determining unit 812 is adapted to determine the uploaded cookie as a cross-site cookie when the number of times the cookie is stored on the browser side exceeds a number threshold; and/or determining the cookie as a cross-site cookie when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored.
Optionally, the list generating unit 814 is adapted to generate a cookie database table according to the basic information of the determined cross-site cookie, and generate a cross-domain database table according to the cross-site information of the determined cross-site cookie, where the cookie list is formed by the cookie database table and the cross-domain database table; and/or generating a website list according to JS scripts for executing cross-site cookie writing operation or url of HTTP return headers in the form of iframe.
Optionally, the list generating unit 814 is adapted to obtain the number of different websites visited by the browser when the same cookie is stored, and arrange urls of the HTTP return headers in the form of JS scripts or iframes in order of the number from high to low to obtain the website list.
The specific working modes of the units in the device embodiment of the invention can be seen in the corresponding method embodiment of the invention.
The embodiment of the invention can acquire the cookie of the website for tracking the user behavior by collecting the cookie of each browser side and determining the technical means of cross-site cookie tracking the user behavior; by means of the technical means that the cookie lists and/or the website lists are generated according to the cross-site cookies and issued to the browser sides, the browser sides can acquire the cross-site cookies, so that the browser sides can only forbid storage of cookie information of third-party websites for user behavior tracking, the problems that in the prior art, storage of cookies of all third-party websites is forbidden, network performance is poor, and network operation is not smooth enough are solved, safety of user privacy data can be improved, and network performance and smoothness of network operation are guaranteed.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that microprocessors or Digital Signal Processors (DSPs) may be used in practice to implement some or all of the functionality of some or all of the components in browsers and servers according to embodiments of the invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
The embodiment of the invention discloses A1 and a method for processing cookie information, which comprises the following steps:
collecting cookies uploaded by each browser side;
determining a cross-site cookie tracking user behavior according to the cookie;
generating a cookie list of the cross-site cookie and/or a website list of a website to which the cross-site cookie belongs according to the cross-site cookie;
and distributing the cookie list and/or the website list to each browser side.
A2, the method according to A1, wherein the collecting cookies uploaded by each browser side includes:
collecting basic information of the cookie uploaded by each browser side, wherein the basic information comprises a main key, creation time, a host where the cookie is located, a name, a value and expiration time; and the number of the first and second groups,
collecting cross-site information of cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
A3, the method of A1, wherein the determining a cross-site cookie to track user behavior from the cookie comprises:
determining the cookie uploaded by the browser side as a cross-site cookie; or,
and determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored.
A4, the method according to A3, wherein the determining the cross-site cookie according to the storage times of the uploaded cookie and/or the number of websites visited by the browser when the cookie is stored comprises:
when the storage times of the uploaded cookies on the browser side exceed a time threshold value, determining the cookies as cross-site cookies; and/or the presence of a gas in the gas,
when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored, the cookie is determined to be a cross-site cookie.
A5, the method according to A2, wherein the generating a cookie list of cross-site cookies and/or a website list of websites to which the cross-site cookies belong according to the cross-site cookies comprises:
generating a cookie database table according to the determined basic information of the cross-site cookie, generating a cross-domain database table according to the determined cross-site information of the cross-site cookie, and forming a cookie list by the cookie database table and the cross-domain database table;
and/or the presence of a gas in the gas,
and generating the website list according to JS script for executing cross-site cookie write operation or url of HTTP return header in an iframe form.
A6, the method according to A2, wherein the generating the website list according to the URL of the HTTP return header in the form of the JS script or the iframe that performs the cross-site cookie write operation includes:
and acquiring the number of different websites visited by the browser when the same cookie is stored, and arranging urls of HTTP return headers in the JS script or iframe form according to the sequence of the number from high to low to obtain the website list.
The embodiment of the invention also discloses B7 and a server, which comprises:
the collecting unit is suitable for collecting the cookies uploaded by each browser side;
a cross-site cookie determining unit, which is suitable for determining a cross-site cookie tracking user behavior according to the cookie;
the list generating unit is suitable for generating a cookie list of the cross-site cookie and/or a website list of websites to which the cross-site cookie belongs according to the cross-site cookie;
and the list issuing unit is suitable for distributing the cookie list and/or the website list to each browser side.
B8, the server according to B7, wherein the collecting unit is adapted to collect basic information of the cookie uploaded on each browser side, the basic information including a primary key, creation time, host where the cookie is located, name, value and expiration time; and collecting cross-site information of cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
B9, the server according to B7, wherein the cross-site cookie determining unit is adapted to determine the cookie uploaded by the browser side as a cross-site cookie; or determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored.
B10, the server according to B9, wherein the cross-site cookie determining unit is adapted to determine the uploaded cookie as a cross-site cookie when the storage number of the cookie on the browser side exceeds a number threshold; and/or determining the cookie as a cross-site cookie when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored.
B11, the server according to B8, wherein the list generation unit is suitable for generating a cookie database table according to the basic information of the determined cross-site cookie, and generating a cross-domain database table according to the cross-site information of the determined cross-site cookie, and the cookie list is formed by the cookie database table and the cross-domain database table; and/or generating the website list according to JS scripts for executing cross-site cookie writing operation or url of HTTP return headers in the form of iframe.
And B12, the server according to B8, wherein the list generation unit is adapted to obtain the number of different websites visited by the browser when storing the same cookie, and arrange the urls of the HTTP return headers in the form of the JS scripts or iframes in descending order according to the number to obtain the website list.
Claims (10)
1. A method of processing cookie information, comprising:
collecting cookies uploaded by each browser side;
determining a cross-site cookie tracking user behavior according to the cookie;
generating a cookie list of the cross-site cookie and/or a website list of a website to which the cross-site cookie belongs according to the cross-site cookie;
and distributing the cookie list and/or the website list to each browser side.
2. The method of claim 1, wherein collecting cookies uploaded by each browser side comprises:
collecting basic information of the cookie uploaded by each browser side, wherein the basic information comprises a main key, creation time, a host where the cookie is located, a name, a value and expiration time; and the number of the first and second groups,
collecting cross-site information of cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
3. The method of claim 1, wherein determining from the cookie a cross-site cookie that tracks user behavior comprises:
determining the cookie uploaded by the browser side as a cross-site cookie; or,
and determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored.
4. A method as claimed in claim 3, wherein determining a cross-site cookie based on the number of times the uploaded cookie was stored and/or the number of websites visited by the browser at the time the cookie was stored comprises:
when the storage times of the uploaded cookies on the browser side exceed a time threshold value, determining the cookies as cross-site cookies; and/or the presence of a gas in the gas,
when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored, the cookie is determined to be a cross-site cookie.
5. The method of claim 2, wherein the generating a cookie list of the cross-site cookie and/or a website list of websites to which the cross-site cookie belongs from the cross-site cookie comprises:
generating a cookie database table according to the determined basic information of the cross-site cookie, generating a cross-domain database table according to the determined cross-site information of the cross-site cookie, and forming a cookie list by the cookie database table and the cross-domain database table;
and/or the presence of a gas in the gas,
and generating the website list according to JS script for executing cross-site cookie write operation or url of HTTP return header in an iframe form.
6. The method of claim 2, wherein the generating the list of websites from the url of the HTTP return header in the form of a JS script or an iframe that performs a cross-site cookie write operation comprises:
and acquiring the number of different websites visited by the browser when the same cookie is stored, and arranging urls of HTTP return headers in the JS script or iframe form according to the sequence of the number from high to low to obtain the website list.
7. A server, comprising:
the collecting unit is suitable for collecting the cookies uploaded by each browser side;
a cross-site cookie determining unit, which is suitable for determining a cross-site cookie tracking user behavior according to the cookie;
the list generating unit is suitable for generating a cookie list of the cross-site cookie and/or a website list of websites to which the cross-site cookie belongs according to the cross-site cookie;
and the list issuing unit is suitable for distributing the cookie list and/or the website list to each browser side.
8. The server according to claim 7, wherein the collecting unit is adapted to collect basic information of the cookie uploaded on each browser side, the basic information including a primary key, a creation time, a host where the cookie is located, a name, a value, and an expiration time; and collecting cross-site information of cookies uploaded by each browser side, wherein the cross-site information of the cookies comprises: a uniform resource locator url of an HTTP return header in the form of a JS script or iframe, a home frame url of a website accessed by the browser side when storing the cookie, a home key, a creation time, and a last access time.
9. The server according to claim 7, wherein the cross-site cookie determination unit is adapted to determine a cookie uploaded on a browser side as a cross-site cookie; or determining the cross-site cookie according to the storage frequency of the uploaded cookie on the browser side and/or the number of websites visited by the browser when the cookie is stored.
10. The server according to claim 9, wherein the cross-site cookie determination unit is adapted to determine the uploaded cookie as a cross-site cookie when the number of times the cookie is stored on the browser side exceeds a number threshold; and/or determining the cookie as a cross-site cookie when the number of different websites visited by the browser exceeds a number threshold when the same cookie is stored.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310551633.7A CN103618696B (en) | 2013-11-07 | 2013-11-07 | Method and server for processing cookie information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310551633.7A CN103618696B (en) | 2013-11-07 | 2013-11-07 | Method and server for processing cookie information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103618696A true CN103618696A (en) | 2014-03-05 |
| CN103618696B CN103618696B (en) | 2017-04-19 |
Family
ID=50169400
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310551633.7A Active CN103618696B (en) | 2013-11-07 | 2013-11-07 | Method and server for processing cookie information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103618696B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103944995A (en) * | 2014-04-28 | 2014-07-23 | 东华大学 | Method for recognizing accounts of independent users in broadband network |
| CN104468790A (en) * | 2014-12-09 | 2015-03-25 | 北京奇虎科技有限公司 | Method for processing cookie data and client side |
| CN105490993A (en) * | 2014-09-19 | 2016-04-13 | 腾讯科技（深圳）有限公司 | Method and apparatus for preventing Cookie tracking in browser |
| CN105847422A (en) * | 2016-05-16 | 2016-08-10 | 乐视控股（北京）有限公司 | User tracking method and server |
| CN106599709A (en) * | 2015-10-15 | 2017-04-26 | 中兴通讯股份有限公司 | Privacy information leakage prevention method and device as well as terminal |
| CN106708878A (en) * | 2015-11-16 | 2017-05-24 | 北京国双科技有限公司 | Terminal identification method and device |
| CN106919595A (en) * | 2015-12-25 | 2017-07-04 | 阿里巴巴集团控股有限公司 | A kind of method, device and electronic equipment mapped for Cookie |
| CN107332723A (en) * | 2016-04-28 | 2017-11-07 | 华为技术有限公司 | The detection method and detection device of convert channel |
| CN107704605A (en) * | 2017-10-13 | 2018-02-16 | 北京中教在线科技有限公司 | It is a kind of based on the user behavior recording method being locally stored |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101482882A (en) * | 2009-02-17 | 2009-07-15 | 阿里巴巴集团控股有限公司 | Method and system for cross-domain treatment of COOKIE |
| CN101540734A (en) * | 2008-03-21 | 2009-09-23 | 阿里巴巴集团控股有限公司 | Method, system and device for accessing Cookie by crossing domain names |
| US20120054846A1 (en) * | 2010-08-31 | 2012-03-01 | John Lightsey | Method for prevention of cross site request forgery attack |
| CN102682009A (en) * | 2011-03-11 | 2012-09-19 | 腾讯科技（北京）有限公司 | Method and system for logging in webpage |
| CN102970284A (en) * | 2012-11-05 | 2013-03-13 | 北京奇虎科技有限公司 | User information processing method and server |
| US20130117817A1 (en) * | 2011-11-07 | 2013-05-09 | Qualcomm Incorporated | Prevention of cross site request forgery attacks by conditional use cookies |
-
2013
- 2013-11-07 CN CN201310551633.7A patent/CN103618696B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101540734A (en) * | 2008-03-21 | 2009-09-23 | 阿里巴巴集团控股有限公司 | Method, system and device for accessing Cookie by crossing domain names |
| CN101482882A (en) * | 2009-02-17 | 2009-07-15 | 阿里巴巴集团控股有限公司 | Method and system for cross-domain treatment of COOKIE |
| US20120054846A1 (en) * | 2010-08-31 | 2012-03-01 | John Lightsey | Method for prevention of cross site request forgery attack |
| CN102682009A (en) * | 2011-03-11 | 2012-09-19 | 腾讯科技（北京）有限公司 | Method and system for logging in webpage |
| US20130117817A1 (en) * | 2011-11-07 | 2013-05-09 | Qualcomm Incorporated | Prevention of cross site request forgery attacks by conditional use cookies |
| CN102970284A (en) * | 2012-11-05 | 2013-03-13 | 北京奇虎科技有限公司 | User information processing method and server |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103944995A (en) * | 2014-04-28 | 2014-07-23 | 东华大学 | Method for recognizing accounts of independent users in broadband network |
| CN103944995B (en) * | 2014-04-28 | 2017-06-06 | 东华大学 | A kind of method of separate user accounts in identification broadband network |
| CN105490993A (en) * | 2014-09-19 | 2016-04-13 | 腾讯科技（深圳）有限公司 | Method and apparatus for preventing Cookie tracking in browser |
| CN105490993B (en) * | 2014-09-19 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Method and device for preventing Cookie tracking in browser |
| CN104468790A (en) * | 2014-12-09 | 2015-03-25 | 北京奇虎科技有限公司 | Method for processing cookie data and client side |
| CN104468790B (en) * | 2014-12-09 | 2018-09-11 | 北京奇虎科技有限公司 | The processing method and client of cookie data |
| CN106599709A (en) * | 2015-10-15 | 2017-04-26 | 中兴通讯股份有限公司 | Privacy information leakage prevention method and device as well as terminal |
| CN106708878B (en) * | 2015-11-16 | 2020-06-16 | 北京国双科技有限公司 | Terminal identification method and device |
| CN106708878A (en) * | 2015-11-16 | 2017-05-24 | 北京国双科技有限公司 | Terminal identification method and device |
| CN106919595A (en) * | 2015-12-25 | 2017-07-04 | 阿里巴巴集团控股有限公司 | A kind of method, device and electronic equipment mapped for Cookie |
| CN107332723A (en) * | 2016-04-28 | 2017-11-07 | 华为技术有限公司 | The detection method and detection device of convert channel |
| CN107332723B (en) * | 2016-04-28 | 2020-09-04 | 华为技术有限公司 | Detection method and detection equipment for hidden channel |
| CN105847422A (en) * | 2016-05-16 | 2016-08-10 | 乐视控股（北京）有限公司 | User tracking method and server |
| CN107704605A (en) * | 2017-10-13 | 2018-02-16 | 北京中教在线科技有限公司 | It is a kind of based on the user behavior recording method being locally stored |
| CN107704605B (en) * | 2017-10-13 | 2021-04-09 | 北京中教在线科技有限公司 | User behavior recording method based on local storage |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103618696B (en) | 2017-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103618696B (en) | Method and server for processing cookie information | |
| Krishnamurthy et al. | Privacy leakage vs. protection measures: the growing disconnect | |
| CN103368957B (en) | Method and system that web page access behavior is processed, client, server | |
| CN101582887B (en) | Safety protection method, gateway device and safety protection system | |
| FaizKhademi et al. | FPGuard: Detection and prevention of browser fingerprinting | |
| US9792365B2 (en) | Method and system for tracking and gathering multivariate testing data | |
| US9300755B2 (en) | System and method for determining information reliability | |
| Gervais et al. | Quantifying web adblocker privacy | |
| CN106033579B (en) | Data processing method and device | |
| WO2017113677A1 (en) | User behavior data processing method and system | |
| KR20070054391A (en) | Apparatus and method for blocking access to phishing web page | |
| CN102663052B (en) | Method and device for providing search results of search engine | |
| US10043038B2 (en) | Identifying private information from data streams | |
| JP2012504288A (en) | Evaluating online marketing efficiency | |
| CN104050178A (en) | Internet monitoring anti-spamming method and device | |
| US20190289085A1 (en) | System and method for tracking online user behavior across browsers or devices | |
| CN109450879A (en) | User access activity monitoring method, electronic device and computer readable storage medium | |
| CN102833212A (en) | Webpage visitor identity identification method and system | |
| CN107800686B (en) | Phishing website identification method and device | |
| CN104079531A (en) | Hotlinking detection method, system and device | |
| CN103559203A (en) | Method, device and system for web page sorting | |
| CN104219230A (en) | Method and device for identifying malicious websites | |
| CN103618761B (en) | Method and browser for processing cookie information | |
| CN110929129B (en) | Information detection method, equipment and machine-readable storage medium | |
| US7974998B1 (en) | Trackback spam filtering system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220801 Address after: Room 801, 8th floor, No. 104, floors 1-19, building 2, yard 6, Jiuxianqiao Road, Chaoyang District, Beijing 100015 Patentee after: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Address before: 100088 room 112, block D, 28 new street, new street, Xicheng District, Beijing (Desheng Park) Patentee before: BEIJING QIHOO TECHNOLOGY Co.,Ltd. Patentee before: Qizhi software (Beijing) Co.,Ltd. |