Cookies: Difference between revisions
No edit summary |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 9: | Line 9: | ||
== Introduction == | == Introduction == | ||
An HTTP Cookie (web cookie, browser cookie, internet cookie, or cookie) is a small piece of data that a server sends to the user's web browser. This process takes place while the user is using the web browser. | An HTTP Cookie (web cookie, browser cookie, internet cookie, or cookie) is a small piece of data that a server sends to the user's web browser. This process takes place while the user is using the web browser. <ref>https://en.wikipedia.org/wiki/HTTP_cookie</ref> Cookies were designed to be a reliable mechanism for websites to remember stateful information (such as items added in the shopping cart in an online store) or to record the user's browsing activity (including clicking particular buttons, logging in, or recording which pages were visited in the past). They can also be used to remember arbitrary pieces of information that the user previously entered into form fields such as names, addresses, passwords, and credit card numbers. | ||
== How does it work or a deeper look == | == How does it work or a deeper look == |
Latest revision as of 15:23, 30 May 2018
This is student work which has not yet been approved as correct by the instructor
![](/images/6/65/Studying.png)
Introduction[edit]
An HTTP Cookie (web cookie, browser cookie, internet cookie, or cookie) is a small piece of data that a server sends to the user's web browser. This process takes place while the user is using the web browser. [2] Cookies were designed to be a reliable mechanism for websites to remember stateful information (such as items added in the shopping cart in an online store) or to record the user's browsing activity (including clicking particular buttons, logging in, or recording which pages were visited in the past). They can also be used to remember arbitrary pieces of information that the user previously entered into form fields such as names, addresses, passwords, and credit card numbers.
How does it work or a deeper look[edit]
- If you are discussing a THING YOU CAN TOUCH, you must explain how it works, and the parts it is made of. Google around for an "exploded technical diagram" of your thing, maybe like this example of an MRI It is likely you will reference outside links. Please attribute your work.
- If you are discussing a PROCESS OR ABSTRACT CONCEPT (like fuzzy logic) you must deeply explain how it works.
Examples[edit]
Please include some example of how your concept is actually used. Your example must include WHERE it is used, and WHAT IS BENEFIT of it being used.
Pictures, diagrams[edit]
Pictures and diagrams go a LONG way to helping someone understand a topic. Especially if your topic is a little abstract or complex. Using a picture or diagram is a two part process:
External links[edit]
- https://en.wikipedia.org/wiki/HTTP_cookie
- https://www.techopedia.com/definition/7624/cookie
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies
- to help fellow students
- Please make sure the content is good
- and don't link to a google search results, please