On Tue, 02 Dec 2014 21:41:33 +, 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
Ah, I see. That makes sense. Thanks.
---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---
BEGIN:VCARD
VERSION:3.0
N:Brewster;Israel;;;
FN:Israel
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
On Dec 2, 2014, at 4:33 AM, random...@fastmail.us wrote:
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,
On Mon, 01 Dec 2014 11:28:42 -0900, Israel Brewster wrote:
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,
In pan.2014.12.02.21.05.18.838000@nowhere.invalid Nobody
nobody@nowhere.invalid writes:
On Mon, 01 Dec 2014 11:28:42 -0900, Israel Brewster wrote:
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
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
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
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
On Monday, December 1, 2014 12:29:04 PM UTC-8, 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
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
Tim Chase wrote:
I
haven't investigated recently, but I remember Django's ability to
trigger a log-out merely via a GET was something that irked me.
All this to also say that performing non-idempotent actions on a GET
request is just begging for trouble. ;-)
ACK. However, isn't log-out
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
On 2014-12-01 22:44, Christoph M. Becker wrote:
Tim Chase wrote:
haven't investigated recently, but I remember Django's ability to
trigger a log-out merely via a GET was something that irked me.
All this to also say that performing non-idempotent actions on a
GET request is just
On 2014-12-01 16:50, Ned Batchelder wrote:
On 12/1/14 4:26 PM, Tim Chase wrote:
All this to also say that performing non-idempotent actions on a
GET request is just begging for trouble. ;-)
This is the key point: your web application shouldn't be doing
these kinds of actions in response to
On Dec 1, 2014, at 12:50 PM, Ned Batchelder n...@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
On Dec 1, 2014, at 1:12 PM, Tim Chase python.l...@tim.thechases.com wrote:
On 2014-12-01 16:50, Ned Batchelder wrote:
On 12/1/14 4:26 PM, Tim Chase wrote:
All this to also say that performing non-idempotent actions on a
GET request is just begging for trouble. ;-)
This is the key point:
On 2014-12-01 13:14, Israel Brewster wrote:
On Dec 1, 2014, at 12:50 PM, Ned Batchelder n...@nedbatchelder.com
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
18 matches
Mail list logo
