Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!newsreader4.netcologne.de!news.netcologne.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <8744287.J7NaK4W3va@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Tue, 15 May 2012 20:21:33 +0200 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 7Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 23 NNTP-Posting-Date: 15 May 2012 20:21:33 CEST NNTP-Posting-Host: bd704c85.newsspool3.arcor-online.net X-Trace: DXC==29J?D7S?0HE4ZB2flKORAMcF=Q^Z^V3H4Fo<]lROoRA8kFK@U@3`]Ai;BfBUEKccg Swifty wrote: >> Alternatively, you could arrange to redirect requests for [example.com] >> to [www.example.com] > > I think alternatively you could set the cookie domain to [".example.com"], > which includes ["example.com"] and ["www.example.com"], as well as > ["blah.example.com"]. According to my tests, that is equivalent to setting the domain to "example.com". (You should not use potentially existing domain names for examples, see RFC 2606.) PointedEars -- realism: HTML 4.01 Strict evangelism: XHTML 1.0 Strict madness: XHTML 1.1 as application/xhtml+xml -- Bjoern Hoehrmann