A typical use of cookies is the need to remember personal settings for visited websites, for example in forums. Thus, a website can be visited without having to log in each time. For safety reasons this is often not done, in areas such as electronic banking in contrast to forums. HTTP is a stateless protocol, therefore, is for the web server access each independent of all others, past and future.
A Computer Repair Shop in Sydney whose interaction with the user drags over time (multiple HTTP requests) must work with tricks to the participants to be able to identify several requests quickly. The cookie uses a unique session ID stored in the server so as to to accurately recognize this client in successive runs, and thus eliminating the need to be re-enter the password every time.
Online stores may use cookies to collect goods in virtual shopping baskets. The customer can thus add to the shopping cart and continue to look on the website, then buy the items together as handled by the Computer Repair Shop in Sydney.
The identification of the basket or the user’s session cookie is stored in the article IDs assigned to the cart or the user’s session on the server. Only when ordering is this information evaluated on the server side. HTTP cookies also ensure that user actions and entries are not lost when the server crashes when connecting to the web applications, cookies can be used for temporary storage.
When restoring the connection, they are queried from the server. The web application recognizes the order in which the cookies were produced and marks already processed cookies or deletes their contents.
Operation
There are two possibilities for the transfer, assignment and evaluation of cookies by a website. Transmission in the header of queries and responses via HTTP. Cookies in the client arise when accessing a web server in addition to other HTTP headers in the response of the server.
A cookie can be generated locally through JavaScript or other scripting languages. The script is located in the Web page sent by the server. The cookies from the same local domain – not on other sites – can be read, recycled and changed. Thus, information about the local user activities can be incorporated, for example, by Javascript, without further contact with the server.
They are transferred there in the HTTP headers on the next contact with the website. Cookie information is stored locally in the browser, usually in a cookie text file. Further in subsequent accesses to the web server, the client browser searches out all cookies from this domain that fit the Web server and the directory path of the current call. This cookie data is transmitted in the header of the HTTP access, so the cookies may only go back to those web servers from which they came once.
No Comments