Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81816 > unrolled thread
| Started by | random832@fastmail.us |
|---|---|
| First post | 2014-12-02 17:24 -0500 |
| Last post | 2014-12-02 17:24 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Cherrypy - prevent browser "prefetch"? random832@fastmail.us - 2014-12-02 17:24 -0500
| From | random832@fastmail.us |
|---|---|
| Date | 2014-12-02 17:24 -0500 |
| Subject | Re: Cherrypy - prevent browser "prefetch"? |
| Message-ID | <mailman.16502.1417559107.18130.python-list@python.org> |
On Tue, Dec 2, 2014, at 10:59, 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. As I understand it, the usual way to do this these days is to have a link which, A) when navigated to, provides a simple standalone form confirming the action with a button and B) when clicked on with a browser with javascript enabled, automatically submits a hidden form, or an AJAX/JSON request or something, to accomplish the same task skipping the standalone page entirely. This will also have the effect of keeping these entries out of your browser history. Any action which has harmful or annoying side effects should definitely not be a GET.
Back to top | Article view | comp.lang.python
csiph-web