PHP sends cookies in the header information of the http protocol, so the setcookie() function must be called before other information is output to the browser, which is similar to the restriction on the header() function.
1. Set cookie:
a .
eg:
Php code
b.
header("Set-Cookie: name=$value[;path=$path[;domain=xxx.com[ ;...]]");
Php code
You can read browser-side cookies directly using PHP's built-in super global variable $_COOKIE.
eg:
3.
Just set the valid time to be less than the current time, and set the value to empty. For example:
eg:
Php code
Use header() similar.
Note:
a.
b.
c.
4. Principle.
a. The server sends an http with the response Set-Cookie header, sets a cookie in the client (multiple cookies require multiple headers).
b. The client automatically sends an http cookie header to the server, and the server receives and reads it.
HTTP/1.x 200 OK
MT
Cache -Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
use using using using ’ ’ s ’ s ’ s ‐ ‐ ‐ ‐ t , after receiving this line
Set-Cookie: TestCookie=something from somewhere; path=/
TestCookie=something from somewhere;
This line is the result of us using setcookie('TestCookie','something from somewhere','/'); That is the result of using
---------------------------------------- ---------Dividing line--------------------------------------- --------------------------------
PHP SESSION
The core concept of session is: extra data for jumping between web pages is saved on the server and identified by an ID. To maintain the session, the browser needs to bring this ID with each submission.
------------------------------------------------ -------------------------------------------------- ----------------------------------
There are two ways to pass session id:
a.
When you jump to a new page from this page and call session_start(), PHP will check the server-side storage associated with the given ID session data, if not found, create a new data set.
b
xxx, session can also be passed through POST value.
If the client prohibits the use of cookies, you can use the following Method:
a. Set session.use_trans_sid = 1 in php.ini or turn on the --enable-trans-sid option when compiling to let PHP automatically pass the session id across pages.
b. Manually pass the value through the URL and pass the session id through the hidden form.
c. Save session_id in a file, database, etc., and call it manually during the cross-page process.
link: http://apps.hi.baidu.com/share/detail/41643457
session can also be used when cookies are disabled: session.use_cookies in
php.ini =1, change it to 0, the session will be saved on the server side, not the client's cookie.
You can view the server's session storage location through session.save_path
session usage:
eg:
Php code
var_dump(
$_SESSION
'',time()-3600);
// Step 2: Delete the actual session:
$_SESSION
array();
// Step 3: Delete $_SESSION global variable array
------------------------ -------------------------------------------------- -------------------------------------------------- --
A simple example:
php code:
Php code
Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control : no -store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache
Content-Length: 1Keep-Alive: timeout=15, max=99 Connection: Keep -Alive Content-Type: text/html; charset=utf-8 Content-Language: Off
Second request to the server:
GET /test.php HTTP/1.1
Accept: */*
Referer: http://localhost/
Accept-Language: zh-cn
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Maxthon; .NET CLR 1.1.4322) Host: localhost Connection: Keep-Alive Cookie: PHPSESSID=bmmc3mfc94ncdr15ujitjogma3
Second server Returns:
HTTP/1.1 200 OK Continue to look at the second request to the server, and the cookie PHPSESSID is still sent to the server The following conclusions can be drawn: 1. As long as the session is used, the session will be sent to the client browser through the cookie In fact, session is a completely abstract concept. What session really does is, in addition to the parameters provided by http and post, is to target a user (maybe a browser, or a computer, or even It is an IP) that can save additional information. If we don't use the session provided by the system, we can also transfer data. For example, the data we originally want to store in the session can be serialized and then encrypted to form a string and passed in all URLs and forms on the page. After the server receives the page request, it takes out the secret string from get or post, uncovers it, and restores the data. This is actually the same thing as the session. It's just that this method is super bt, and it requires too much extra work to implement. From a technical point of view, session is to name the additional data to be stored between web page links with an ID and save it on the server side. The browser only needs to provide the appropriate ID for each get or post. Can obtain previously stored data. PHP uses files to save data by default. Under Unix, PHP will generally create a file name like "sess_"+$session_id under /tmp. Through this name, you can directly find the data corresponding to session_id. Therefore, the most core concept of session is: additional data for jumping between web pages is stored on the server and identified with an ID. To maintain the session, the browser needs to bring this ID with each submission.
The above introduces the PHP version - HTTP session cookie principle and application, including the relevant content. I hope it will be helpful to friends who are interested in PHP tutorials.
Date: Fri, 26 Aug 2005 07:44:23 GMT
Server: Apache/2.0.54 (Win32) SVN/1.2.1 PHP/5.0.4 DAV/2
X- Powered-By: PHP/5.0.4
Set-Cookie: PHPSESSID=bmmc3mfc94ncdr15ujitjogma3; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must- revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 1
Keep-Alive: timeout=15, max=98
Connection: Keep-Alive
Content-Type: text/ html; charset=utf-8
Content-Language: OFF This The header will send a cookie information to the server, telling the server that I have a cookie named PHPSESSID and the content is bmmc3mfc94ncdr15ujitjogma3. Where did this cookie come from? Look at the information returned by the server for the first time: Set-Cookie: PHPSESSID=bmmc3mfc94ncdr15ujitjogma3; path=/
How can the browser bring this ID with every request? The stupid way is of course to add an ID parameter to each URL link or form post. Some webmails actually do this. Of course, the easier way is to save it through cookies. But there is still a problem with the cookie solution. What to do if the browser does not support cookies? This is also stated above. The above session is the session function provided by php4 and 5. You must know that the system did not provide the session function before php4! And many cgi programs are completely self-implemented sessions. For sessions provided by php(4,5), the system will use cookies to save session_id by default. In my previous project, users all used the web on the intranet. In order to facilitate management, the browser IP is directly tied to a session, that is, the browser IP address is used instead of the sessionid. There is no cookie in this solution, but it is still a session, because it does not fall outside the definition of session.
Every time a request is made to the server, the local browser will attach the cookie to the request information In fact, it has nothing to do with the session, it is just about how cookies work in the http protocol. This cookie is written by the session_start() function. We can also write the cookie arbitrarily. As long as it is written and the validity period has not expired, the browser can send it.