📄 page_204.html
字号:
<HTML> <HEAD> <!--SCRIPT LANGUAGE="JavaScript" SRC="http://a1835.g.akamai.net/f/1835/276/3h/www.netlibrary.com/include/js/dictionary_library.js"></SCRIPT> <SCRIPT LANGUAGE="JavaScript"> if (!opener){document.onkeyup=parent.turnBookPage;} </SCRIPT!--> <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"><META http-equiv="Content-Type" content="text/html; charset=windows-1252"><SCRIPT>var PrevPage="Page_203";var NextPage="Page_205";var CurPage="Page_204";var PageOrder="213";</SCRIPT> <TITLE>Document</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF"><CENTER><TABLE BORDER=0 WIDTH=100% CELLPADDING=0><TR><TD ALIGN=CENTER> <TABLE BORDER=0 CELLPADDING=2 CELLSPACING=0 WIDTH=100%> <TR> <TD ALIGN=LEFT><A HREF='Page_203.html'>Previous</A></TD> <TD ALIGN=RIGHT><A HREF='Page_205.html'>Next</A></TD> </TR> </TABLE></TD></TR><TR><TD ALIGN=LEFT><P><A NAME='JUMPDEST_Page_204'/><A NAME='{6F6}'/><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH='100%'><TR><TD ALIGN=RIGHT><FONT FACE='Times New Roman, Times, Serif' SIZE=2 COLOR=#FF0000>Page 204</FONT></TD></TR></TABLE><A NAME='{6F7}'/><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><TR> <TD ROWSPAN=5></TD> <TD COLSPAN=3 HEIGHT=12></TD> <TD ROWSPAN=5></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR><TD></TD> <TD><FONT FACE='Times New Roman, Times, Serif' SIZE=3>created by servers on visiting browsers' hard disks that contain an identification code. They are passed by servers to browsers so that each time a website visitor returns to a server that passed the cookie it can recognize it and read what it wrote before, such as what pages were visited during the prior session. Netscape developed cookies as a means for servers to identify a specific browser, with the specification that only the server that provided the cookie can be the one that can access it and retrieve it. This means that identification cookie codes sent to your cookie.txt file by another server could not be accessed by a different website. Cookies unfortunately are limited to identifying browsers, not individuals.</FONT></TD><TD></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR> <TD COLSPAN=3 HEIGHT=1></TD></TR></TABLE><A NAME='{6F8}'/><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><TR> <TD ROWSPAN=5></TD> <TD COLSPAN=3 HEIGHT=12></TD> <TD ROWSPAN=5></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR><TD></TD> <TD><FONT FACE='Times New Roman, Times, Serif' SIZE=3>Every visit by your customers to your website is a separate event, totally unconnected or related to any previous connection or event. Cookies are a technique by which you can make these unrelated events link into a semblance of a real-world transaction, such as the shopping experience. In fact, cookies were developed by Netscape software developers in an effort to create a shopping cart application. The shopping cart analogy works this way: it allows shoppers to buy more than one item at a session as they wander through the store (website) and pay at the cash register (form) as they leave the store. What is also important is that the store now has a record of which person went where in the store and what items were purchased. Similar to the way you order from a cataloger, a website using cookies is able to record what items you like and purchase over time and how you pay for them.</FONT></TD><TD></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR> <TD COLSPAN=3 HEIGHT=1></TD></TR></TABLE><A NAME='{6F9}'/><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><TR> <TD ROWSPAN=5></TD> <TD COLSPAN=3 HEIGHT=12></TD> <TD ROWSPAN=5></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR><TD></TD> <TD><FONT FACE='Times New Roman, Times, Serif' SIZE=3>Cookies are a hack solution to a problem of "statelessness" caused by the nature of the Web and its protocol, the Hyper Text Transfer Protocol (HTTP). HTTP allows for communications to take place instantaneously without the need to maintain open connections, which may not be needed again. An effective client/server design, but poor retailing environment—hence the need to maintain "state"—cookies. (See Figure 6-1.)</FONT></TD><TD></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR> <TD COLSPAN=3 HEIGHT=1></TD></TR></TABLE><A NAME='{6FA}'/><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><TR> <TD ROWSPAN=5></TD> <TD COLSPAN=3 HEIGHT=12></TD> <TD ROWSPAN=5></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR><TD></TD> <TD><FONT FACE='Times New Roman, Times, Serif' SIZE=3>The usual way cookies work is when a CGI script identifies a new user, it adds an extra header to its response with an identifier for that web visitor and other information that the server may capture from the client's input. This new header data informs the browser to add this information to the client's cookie file. In Netscape it is added to the cookie.txt file; in Internet Explorer, cookies are kept in a cookie directory under the Windows directory, associated with the username taken from the login name for the operating system (e.g., "mena@excite.txt").</FONT></TD><TD></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR> <TD COLSPAN=3 HEIGHT=1></TD></TR></TABLE><A NAME='{6FB}'/><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><TR> <TD ROWSPAN=5></TD> <TD COLSPAN=3 HEIGHT=12></TD> <TD ROWSPAN=5></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR><TD></TD> <TD><FONT FACE='Times New Roman, Times, Serif' SIZE=3>Any subsequent request to that URL from the browser will include the cookie information as an extra header in the request. The CGI script uses this information to return a document targeted to that specific web visitor or returning customer. Since the cookie information</FONT><FONT FACE='Times New Roman, Times, Serif' SIZE=3 COLOR=#FFFF00><!-- continue --></FONT></TD><TD></TD></TR><TR> <TD COLSPAN=3></TD></TR><TR> <TD COLSPAN=3 HEIGHT=1></TD></TR></TABLE><A NAME='{6FC}'/></FORM></P></TD></TR></TABLE><P><FONT SIZE=0 COLOR=WHITE></CENTER><A NAME="bottom"> </A><!-- netLibrary.com Copyright Notice --> </BODY></HTML>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -