Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Gregory Ewing Newsgroups: comp.lang.python Subject: Re: Cherrypy - prevent browser "prefetch"? Date: Wed, 03 Dec 2014 19:17:29 +1300 Lines: 13 Message-ID: References: <6B74D6DD-A597-4BCF-8586-D0A56C9CDB77@ravnalaska.net> <1417527181.1832828.197804893.3AA95580@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net aJ7HlxAelJJbhxgX0K1zZw59bZnAtI+KT+h2ZG8SJ2HC7R8JCk Cancel-Lock: sha1:sA/PIT1YI+qKPPqZ4RZiDQ8golQ= User-Agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711) X-Accept-Language: en-us, en In-Reply-To: Xref: csiph.com comp.lang.python:81840 Israel Brewster wrote: > Primary because they aren’t forms, they are links. And links are, by > definition, GET’s. That said, as I mentioned in earlier replies, if using a > form for a simple link is the Right Way to do things like this, then I can > change it. I'd look at it another way and say that an action with side effects shouldn't appear as a simple link to the user. Links are for requesting information; buttons are for triggering actions. -- Greg