I thought the browser then resends the cookie on every consecutive
request to the domain/path specified by the initial "set-cookie"
http header from the server
This doesn't happen automatically, in your page you've got to ask for
it.
Still don't know why they call them cookies, notecards or something
similar makes more sense--or bananas.
On Aug 2, 2009, at 1:56 PM, Michal Charemza wrote:
On 2 Aug 2009, at 19:52, Ryan Florence wrote:
I think you're misunderstanding what a cookie is (or I'm
misunderstanding you).
Well, at least I thought I understood it!
A cookie is a chunk of data that the website tells the browser to
store on the visitors machine.
I thought it did this and one thing more: I thought the browser then
resends the cookie on every consecutive request to the domain/path
specified by the initial "set-cookie" http header from the server
(until the specified expire time). I thought that "disabling"
cookies *might* just stop this "resending" stage.
If the browser has cookies disabled, it will never store a cookie,
and therefore nothing (javascript or otherwise) has access to
something that is nonexistent.
Well... this does now make sense I guess :-) I just thought that it
*might* be possible that the browser has the cookie in memory (and
accessible via JS) on the page that has the initial "set-cookie"
http header, but doesn't keep it in memory on any subsequent pages.
Michal.
