Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Nobody Newsgroups: comp.lang.python Subject: Re: Cherrypy - prevent browser "prefetch"? Date: Wed, 03 Dec 2014 16:09:24 +0000 Organization: A noiseless patient Spider Lines: 19 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="152d4dee6f95183c956ee6fa63d7e69f"; logging-data="5345"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+midmRTlzWdIQjUoBTsdd9" User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Cancel-Lock: sha1:l3uVgu4VBz6mnLgiY+UNXg9Tfp4= Xref: csiph.com comp.lang.python:81865 On Tue, 02 Dec 2014 21:41:33 +0000, John Gordon wrote: > GET shouldn't cause any business data modifications, but I thought it was > allowed for things like logging out of your session. GET isn't supposed to have observable side-effects. "Observable" excludes things like logs and statistics, but getting logged out of your session is definitely observable. X-moz: prefetch, X-Purpose etc (note that these all have X- prefixes, meaning that they're not in any standard) exist because web developers seem to be uniquely bad at distinguishing between specified behaviour and "seems to work". But realistically, this horse is not only out of the barn but half way around the world by now. So many sites misuse GET that there has to be workarounds for it (to be honest, I'm surprised that they haven't made it into a standard yet).