Home >Backend Development >PHP Tutorial >Detailed explanation of HTTP Cookie state management mechanism, detailed explanation of cookie_PHP tutorial

Detailed explanation of HTTP Cookie state management mechanism, detailed explanation of cookie_PHP tutorial

WBOY
WBOYOriginal
2016-07-12 09:00:48837browse

Detailed explanation of HTTP Cookie state management mechanism, detailed explanation of cookies

HTTP cookies, often called "cookies", have existed for a long time, but are still not fully understood . The primary problem is that there are many misunderstandings, thinking that cookies are backdoors or viruses, or simply not knowing how they work. The second problem is the lack of a consistent interface for cookies. Despite these problems, cookies still play such an important role in web development that if cookies disappeared without a replacement, many of our favorite web applications would be rendered useless.

1. Origin of cookies

Cookies were first invented by Netscape employee Lou Montulli in March 1993 and were later adopted by W3C. Currently, cookies have become a standard and are supported by all mainstream browsers such as IE, Chrome, Firefox, Opera, etc.

The birth of cookies is due to the inherent flaws of the HTTP protocol. HTTP is a stateless protocol. Once the request/response is completed, the connection between the client and the server will be closed, and new data needs to be established to exchange data again. connection. This means that the server cannot track the session from the connection, that is, the server does not know which client it is.

Some typical applications such as login/shopping cart cannot be implemented. For example, the products purchased by user A in the shopping mall should be placed in user A's shopping cart. No matter when user A purchases them, they belong to the same session and cannot be placed in user B or user C's shopping cart. , which does not belong to the same session.

The basic principle is as shown in the figure


2. Cookie operation

The operations on cookies include the following

1.Name
2.Value
3.Domain
4.Path
5.Expires
6.Security
7.HttpOnly (server only)

Note that cookies are mostly created on the server side. JS can also create cookies, but HttpOnly type JS cannot create them.

The cookie API (document.cookie) provided by the browser is too simple and can be encapsulated. For example, it is much more convenient to use the setter/getter cookie function as follows

/*
* JS 写cookie和读cookie操作
*
* **取cookie**
* cookie(name)
*
* **写cookie**
* cookie(name, value)
* cookie(name, value, option)
*/
var cookie = function(name, value, option) {
var doc = document
if (value != undefined) { // set 
option = option || {}
if (value === null) {
value = ''
option.expires = -1
}
var expires = ''
if (option.expires && (typeof option.expires == 'number' || option.expires.toUTCString)) {
var date = new Date
if (typeof option.expires == 'number') {
date.setTime(date.getTime() + (option.expires * 24 * 60 * 60 * 1000))
} else {
date = option.expires
}
// for IE
expires = '; expires=' + date.toUTCString()
}
var path = option.path ? '; path=' + option.path : ''
var domain = option.domain ? '; domain=' + option.domain : ''
var secure = option.secure ? '; secure' : ''
doc.cookie = [name, '=', encodeURIComponent(value), expires, path, domain, secure].join('')
} else { // get 
var cookieValue = null
if (doc.cookie && doc.cookie != '') {
var cookies = doc.cookie.split(';')
for (var i = 0; i < cookies.length; i++) {
var cookie = $.trim(cookies[i]).split('=')
if ( cookie[0] == name && cookie.length > 1 ) {
try {
cookieValue = decodeURIComponent(cookie[1])
} catch(e) {
cookieValue = cookie[1]
}
break
}
}
}
return cookieValue
}
}; 

Of course, there is also the more convenient https://github.com/florian/cookie.js, which provides more convenient functions.

3. Cookie type

1. Ordinary cookies can be created by both server side and JS, and can be accessed by JS
2.HttpOnly cookie can only be created by the server and cannot be read by JS. It is mainly based on security considerations
3. Secure cookies (https only), both server-side and JS can be created, JS can only be accessed under HTTPS

For example, when testing the page on Sina Cloud: http://snandy.sinaapp.com/php/cookie.php, I planted 3 cookies, namely c1, c2, c3

$d1 = mktime(1,1,1,1,1,2018);
// 普通cookie
setcookie("c1", "Jack", $d1); 
// 安全的cookie,仅https,第6个参数
setcookie("c2", "John", $d1, NULL, NULL, TRUE); 
// HttpOnly cookie 第7个参数
setcookie("c3", "Resig", $d1, NULL, NULL, NULL, TRUE); 

Visit with Firefox


I have three of them, saeut is from Sina Cloud.

Enter document.cookie
in firebug console


As you can see, c2 and c3 are inaccessible. c2 is a secure cookie and needs to be accessed under the https protocol. c3 is httpOnly and cannot be accessed by JS. This needs to be noted.

Change the access protocol to https: https://snandy.sinaapp.com/php/cookie.php, switch to firebug console and enter document.cookie, you can see c2 and you can access it

4. Cookie Pitfalls

1. When the cookies are too large or there are too many, an error will be reported when accessing the page. For example, the following prompt will appear

Therefore, the site’s cookies need to be managed, and cookies cannot be planted at will. In addition, try to specify the path to limit the cookie to the specified range.

The website browsercookielimits.squawky.net records the cookie size of each browser


2. Unicode encoding (encodeURIComponent) is required when saving Chinese, otherwise the data will be garbled

Articles you may be interested in:

  • Using Microsoft.XMLHTTP control to send COOKIE
  • ASP uses XMLHTTP to implement form submission and cookie sending code
  • AndroidHttpClient uses Cookie application analysis
  • C# HttpClient Cookie verification solution
  • Code for sending HTTP requests with cookies implemented using VBS
  • .net Obtain browser cookies (including HttpOnly ) Example sharing
  • The specific implementation of httpclient simulated login (using js to set cookies)
  • Python imitates POST to submit HTTP data and use cookie values

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/1091854.htmlTechArticleDetailed explanation of HTTP Cookie status management mechanism, detailed explanation of cookie HTTP cookies, often also called "cookies", have existed for a long time for a long time, but it is still not fully understood. First question...
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn