Session tracking Technology Cookieless

Session tracking Technology Cookieless

In Web applications, Cookie is usually used to record the status of users, such as user name, access time and other information. When a HTTP request is made, Cookie information is automatically sent to the server. When received by the server, the user's identity can be judged, the user's behavior can be tracked, and the specific data can be written into the user's Cookie. Users have multiple Cookie, each of which corresponds to a domain name. For example, when a user participates in a vote at a certain time, the server records the vote information in Cookie. When the user votes again, the server will check whether the user is eligible to vote, so as to avoid the behavior of ticket brushing.

Since some browsers and clients do not support Cookie, the server can adopt Cookieless technology at this time. Cookieless is to add an Etage standard string to the URL URL to represent the identity of the user. For example, when a user requests a URL for the first time, the server generates a unique string for that user and then adds the string to each URL in the web page. When the user clicks the URL in the page to access other pages, the server can extract the user's identity information from the requested URL.

Since there is no uniform implementation standard for Etag, the form of the string is not fixed and is determined by the server itself. In the sniffing process, if you grab the request packet of HTTP, there is no Cookie information, but the URL contains irregular strings, which may be the identity information of Cookieless. By adding this information to other URLs on the site, you can obtain the information in that identity.