Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #81802

Re: Cherrypy - prevent browser "prefetch"?

From random832@fastmail.us
Subject Re: Cherrypy - prevent browser "prefetch"?
Date 2014-12-02 08:33 -0500
References <6B74D6DD-A597-4BCF-8586-D0A56C9CDB77@ravnalaska.net>
Newsgroups comp.lang.python
Message-ID <mailman.16493.1417527184.18130.python-list@python.org> (permalink)

Show all headers | View raw


On Mon, Dec 1, 2014, at 15:28, Israel Brewster wrote:
> For example, I have a URL on my Cherrypy app that updates some local
> caches. It is accessed at http://<server>/admin/updatecaches So if I
> start typing http://<server>/a, for example, safari may auto-fill the
> "dmin/updatecaches", and trigger a cache refresh on the server - even
> though I was just trying to get to the main admin page at /admin. Or, it
> might auto-fill "uth/logout" instead (http://<server>/auth/logout), and
> log me out of my session. While the former may be acceptable (after all,
> a cache update, even if not strictly needed, is at least non-harmfull),
> the latter could cause serious issues with usability. So how can cherrypy
> tell the difference between the "prefetch" and an actual request, and not
> respond to the prefetch?

Why is your logout form - or, your update caches form, etc - a GET
instead of a POST? The key problem is that a GET request is assumed by
browser designers to not have any harmful side effects.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: Cherrypy - prevent browser "prefetch"? random832@fastmail.us - 2014-12-02 08:33 -0500

csiph-web