A refresh operation on a browser that does not support cookies will wipe out the session

The sessionid is stored in a cookie and the solution is as follows:

Session URL rewrite to ensure that the session can still be used when cookies are disabled or not supported by the client

session mechanism. The session mechanism is a server-side mechanism where the server uses a structure similar to a hash table (or perhaps a hash table) to store information.

When the program needs to create a session for a client's request, the server first checks whether the client's request contains a session identifier (called the session id), if it does, it means that a session has been created for the client before, and the server retrieves the session according to the session id (if it cannot be retrieved, a new one will be created), if the client request does not contain a session id, then create a session for this client and generate a session ID associated with this session, the value of the session ID should be a string that is not repeated, and it is not easy to find the pattern to imitate, and this session ID will be returned to the client in this response for saving. This session ID can be saved by using a cookie, so that the browser can automatically play this ID to the server according to the rules during the interaction. Usually the name of this cookie is something like SeeesionId.

However, cookies can be artificially blocked, and there must be other mechanisms in place to pass the session ID back to the server when a cookie is disabled.

One technique that is often used is called URL rewriting, which appends the session ID directly to the URL path.

There is also a technique called form hiding fields. This means that the server will automatically modify the form and add a hidden field so that the session ID can be passed back to the server when the form is submitted.

The form hides fields, such as:

URL rewrite:

1 The way to save the session ID can be a cookie, so that the browser can automatically send this ID to the server according to the rules during the interaction.

2 Since cookies can be artificially banned, there must be other mechanisms to pass the session ID back to the server when the cookie is disabled, and a technique often used is called URL rewriting, which is to append the session ID to the URL path, and there are two ways to append it.

a, as additional information for the URL path.

b, appended to the URL as a query string.

In order for the network to remain in state throughout the interaction, the session ID must be appended to all possible paths where the client can send requests

3 There is also a form hidden field, which will automatically modify the form on the server side and add a hidden field (if the value of the hidden field is not placed in the form, it can disgust the person who crawls the page) so that the user can pass the session ID back to the server when submitting the form.

If you use this function, it is easy to have problems when you use the browser again.

For example, if it is QQ Browser, open this browser first.

Then right-click on the top and operate the bottom. You can set the options out.

It's better to keep this cookie on, as long as it's cleaned up in time, it can be used more smoothly on the computer.

With this browser, you can quickly surf the Internet on your computer.