The next time the browser sends a request, all the information in the cookie is sent back to the server. This is a series of name-value pairs to identify the user together with information that's to be preserved between requests. When the server responds, it sends a cookie for the browser to store. The browser sends the request to the web server in the normal way. Cookies are one way of preserving information across multiple requests. This stateless communication makes it impossible to preserve detail such as the visitor's name, preferences, or contents of a shopping cart. Each request and response is treated independently. Apart from knowing where to send everything, the server has no interest in who you are. What that means is the browser sends a request to the web server, and the server responds by sending the requested web page and associated assets, such as images and style sheets. Basic communication between a browser and a web server is stateless. This will lay the foundation for devising a strategy to minimize the risks of persistent sessions that don't require users to log in each time they visit a site. In this chapter, we'll take a detailed look at the security implications of sessions, starting with a very basic overview of How PHP Sessions Work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |