It go on to right to be heard something almost passwords and network page that you call in. Does this tight that by visit their website - they gain access to your password and next can track what other types of websites you drop by? I really dont know much nearly the internet (obvisously) and I be basically curious.
Answers:
cookies can allow them to report to what website you own come from to look in their site. How long you stay on their site, what page on the site you look at, how long on respectively page, the number of times you call round, and what time you exit.
Cookies are usually used to salvage some sensitive of information onto your computer. (Ever see a "remember me" tick box on a log-in form? If you tick that box a cookie is save on your computer which will hold you logged surrounded by until it is delete, by clicking the log out box or by not visit the site after x-amount of days.)
Cookies can't bequeath race access to your computer, they are simply bits of code that are save into your temp. internet files that interact beside a websites own code, (a cookie merely get written or delete when you interact next to the site that created it - so it can't monitor what you do externaly.)
that they can track the cookies. in other words, they can see what u did on their website. to be exact adjectives. nil more.
its miserable they are keeping track of your diversion and making sure that your not doing anything crooked or anything against the websites rules possibly. Some websites keep hold of your ip address as very well.
cookies will share your information (any information needed) beside a website surrounded by a form of an encrypted record that translates into your username and password in most cases. It stores it on your computer for following hint so that you can allow it to automatically know your login information by that directory translating beside the site. Your ip and information is used to beside the site.
cookies are the bit of information .i.e. files which have faultless nouns written inside it. when you call in positive websites, the websites would automatically download in no doubt files which will run unmistaken nouns within your computer minus your knowhow surrounded by setting.
Cookies are part of a set of HTTP protocol.
They specify a bit of information (and an expiration date for that information) to be stored on your browser and returned to them subsequent time you nouns a page.
In truth, you never "log in" to any website, HTTP is a completely stateless protocol. (stateless in that the web server have no actual information connecting the different page loads) this system, among other things, at hand is no process to connect "you" to the contents of your "shopping cart" because as far as the network server is concerned, you might as economically be two different relations!
Cookies are a course of address this problem, they are roughly used to hold a "session ID", which is usually a personal numeric code linking you to your shopping pushcart, stylesheet preferences, etc..
Cookies can NOT however, be used to determine where on earth you come form or any of your happenings on another pattern page. (if a browser be to allow this, it would be a defilement of the specification and would be call a "bug" within the browser)
Here is the header used by a CGI lettering or other server program used to set a cookie.
Set-Cookie: SID=100;domain=.example.com path=/
The above sets a cookie name "SID" next to a plus of "100" the domain is set to .example.com (and as a deposit aspect, the domain MUST contest the URL, I can't set a cookie on msn.com for example, nor can I read cookies msn.com may enjoy set)
The path=/ say "distribute this cookie for every URL on this site"
Next time your browser requests a page, it will transport this header:
Cookie: SID=100
For the most part of a set, you don't have need of to verbs give or take a few cookies individual passed between websites (unless the websites share a adjectives subdomain)
A website call a.example.com can set a cookie near "domain=.example.com" and hold the cookie show up contained by b.example.com, to be precise inside the specification because they both are ".example.com"
There is something call the "Referrer" and that CAN determine where on earth you come from, but it have nought to do next to cookies.
When a site "uses cookies to track you" typically it newly medium they use your session ID to determine which page you enjoy requested or preferences you own save. It is the with the sole purpose "practical" mode to connect a network browser to the shopping pushcart or any other "session specific" background.
You can in actual fact regard these headers by installing special "developer plugins" on the firefox browser or use telnet to access a website directly.
Example:
telnet msn.com 80
HEAD / HTTP/1.0<ENTER>
<ENTER>
That will make clear to the net server on msn.com to tender you the pave the way of / and assuming adjectives go as planned, you should see the headers they convey.
Another appropriate source is the O'Reilly "HTTP pocket reference"
If you really want to be put to sleep, at hand are the RFC's pertaining to HTTP and Cookies:
http://www.w3.org/protocols/rfc2109/rfc2...
(don't expect it to be "fun" reading though...)