From claus.dahl at gmail.com  Thu Oct  6 11:14:13 2005
From: claus.dahl at gmail.com (Claus Dahl)
Date: Thu Oct  6 04:15:15 2005
Subject: [Slogger] Does slogger re POST?
Message-ID: <6e798a2a0510060114j61221c18o72bd9d358927f83d@mail.gmail.com>

Is it possible that Slogger does not honor REST principles? I am
investigating a bug in a web application that's exposed by slogger. It's the
usual kind of problem where the application was not guarding agains
accidental GET requests, so that morphing changes ot the web resource could
happen as a consequence of a GET request. Now however the app seems to be
properly guarded against GET - but my issue with sloggers persists. It's as
if Slogger reruns the request currently displayed in the browser, even if
that was a POST request - which Slogger obviously shouldn't, since that
might delete/update and so on web resources. Has anybody seen somehting like
this or is the app still broken?

Claus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mozdev.org/pipermail/slogger/attachments/20051006/ac99e2b1/attachment.htm
From kschutte at MIT.EDU  Thu Oct  6 11:43:21 2005
From: kschutte at MIT.EDU (Ken Schutte)
Date: Thu Oct  6 10:43:48 2005
Subject: [Slogger] Does slogger re POST?
In-Reply-To: <6e798a2a0510060114j61221c18o72bd9d358927f83d@mail.gmail.com>
References: <6e798a2a0510060114j61221c18o72bd9d358927f83d@mail.gmail.com>
Message-ID: <43453809.6010204@mit.edu>

I'm not sure exactly what you mean, but this may be a bug in Firefox. 
Slogger runs the same code as when you do File->Save As in Firefox.  Try 
that and see if you get the same thing.  I think there was an issue of 
it sending extra GET requests when you save a page.

Ken

Claus Dahl wrote:
> Is it possible that Slogger does not honor REST principles? I am 
> investigating a bug in a web application that's exposed by slogger. It's 
> the usual kind of problem where the application was not guarding agains 
> accidental GET requests, so that morphing changes ot the web resource 
> could happen as a consequence of a GET request. Now however the app 
> seems to be properly guarded against GET - but my issue with sloggers 
> persists. It's as if Slogger reruns the request currently displayed in 
> the browser, even if that was a POST request - which Slogger obviously 
> shouldn't, since that might delete/update and so on web resources. Has 
> anybody seen somehting like this or is the app still broken?
> 
> Claus
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Slogger mailing list
> Slogger@mozdev.org
> http://mozdev.org/mailman/listinfo/slogger
From karen.garrett at comcast.net  Sun Oct 16 05:11:17 2005
From: karen.garrett at comcast.net (karen garrett)
Date: Sun Oct 16 07:12:36 2005
Subject: [Slogger] start
Message-ID: <002b01c5d242$54b83500$2101a8c0@UPSTAIRS>