Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Ben Bacarisse Newsgroups: comp.lang.javascript Subject: Re: Difference between client and server side cookie Date: Sun, 13 Mar 2016 10:42:31 +0000 Organization: A noiseless patient Spider Lines: 27 Message-ID: <87wpp67j6w.fsf@bsb.me.uk> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="017616aa25f81ec581c44d76d61ba2f3"; logging-data="19384"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+uq+drGKNhIaVtDoMml0XbYMydCiJpUm4=" Cancel-Lock: sha1:me3gWboZD8ZJOxR3Idd79jMhhvw= sha1:1yz8Y6KIbRU8rRhu86EXMDVOzuo= X-BSB-Auth: 1.273cecdcad93826822de.20160313104231GMT.87wpp67j6w.fsf@bsb.me.uk Xref: csiph.com comp.lang.javascript:29955 "Evertjan." writes: > Aleksandro wrote on 13 Mar 2016 in > comp.lang.javascript: > >> On 12/03/16 19:32, Evertjan. wrote: >>> Stefan Weiss wrote on 12 Mar 2016 in >>> comp.lang.javascript: >>> >>>> Normally, there is no difference. You can read and set cookies on the >>>> server and on the client (with JS). >>> >>> There are no cookies "on the server". >> >> There are while I am taking care of a request that sent them. > > Take care, that is nonsense. > > I even don't understand your sentense. He's saying that there are sometimes cookies "on the server" -- specifically they are sent there every time a client makes a request for which a cookie is relevant. Where are they while the server is using them if not "on the server"? It's a small point, but it's not wrong. -- Ben.