Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!bcyclone03.am1.xlned.com!bcyclone03.am1.xlned.com!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Cherrypy - prevent browser "prefetch"?
From: Israel Brewster <israel@ravnalaska.net>
In-Reply-To: <m5inqh$kdt$1@ger.gmane.org>
Date: Mon, 1 Dec 2014 13:14:46 -0900
Content-Transfer-Encoding: quoted-printable
References: <6B74D6DD-A597-4BCF-8586-D0A56C9CDB77@ravnalaska.net> <20141201152608.09ca6f13@bigbox.christie.dr> <m5inqh$kdt$1@ger.gmane.org>
To: Ned Batchelder <ned@nedbatchelder.com>
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.16474.1417472090.18130.python-list@python.org>
Lines: 55
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:81782

On Dec 1, 2014, at 12:50 PM, Ned Batchelder <ned@nedbatchelder.com> =
wrote:

> On 12/1/14 4:26 PM, Tim Chase wrote:
>> On 2014-12-01 11:28, Israel Brewster wrote:
>>> I don't know if this is a cherrypy specific question (although it
>>> will be implemented in cherrypy for sure), or more of a general
>>> http protocol question, but when using cherrypy to serve a web app,
>>> is there anyway to prevent browser prefetch? I'm running to a
>>> problem, specifically from Safari on the Mac, where I start to type
>>> a URL, and Safari auto-fills the rest of a random URL matching what
>>> I started to type, and simultaneously sends a request for that URL
>>> to my server, occasionally causing unwanted effects.
>>=20
>> All this to also say that performing non-idempotent actions on a GET
>> request is just begging for trouble. ;-)
>>=20
>=20
> This is the key point: your web application shouldn't be doing these =
kinds of actions in response to a GET request.  Make them POST requests, =
and Safari won't give you any trouble.
>=20
> Trying to stop Safari from making the GET requests might work for =
Safari, but then you will find another browser, or a proxy server, or an =
edge-caching accelerator, etc, that makes the GET requests when you =
don't want them.
>=20
> The way to indicate to a browser that it shouldn't pre-fetch a URL is =
to make it a POST request.

Ok, that makes sense. The only difficulty I have with that answer is =
that to the best of my knowledge the only way to make a HTML link do a =
POST is to use the onclick function to run a javascript, while having =
the "link" itself point to nothing. Just feels a bit ugly to me, but if =
that's the Right Way=99 to do it, then that's fine.

Thanks!

>=20
> --=20
> Ned Batchelder, http://nedbatchelder.com
>=20
> --=20
> https://mail.python.org/mailman/listinfo/python-list


-----------------------------------------------
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------