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


Groups > comp.lang.php > #14933

HTTP (was: Newby neds help)

From "Christoph M. Becker" <cmbecker69@arcor.de>
Newsgroups comp.lang.php
Subject HTTP (was: Newby neds help)
Date 2015-02-10 02:04 +0100
Organization solani.org
Message-ID <mbble7$alq$1@solani.org> (permalink)
References (3 earlier) <mb7o8q$10f$1@dont-email.me> <mb7rf4$ajf$1@solani.org> <mb8lf1$ce8$4@dont-email.me> <mb8s5j$4q9$1@solani.org> <mbb24l$a4b$3@dont-email.me>

Show all headers | View raw


Denis McMahon wrote:

> On Mon, 09 Feb 2015 00:40:37 +0100, Christoph M. Becker wrote:
> 
>> I'm mostly basing my statement on RFC 7231, not on various documents.
> 
>> However, submitting data that are going to be stored on the server
>> (appended to a file) with a GET request, would obviously be a violation
>> of RFC 7231:
> 
> As far as I can tell, RFC 7231 specifies a data transfer protocol. It's 
> outside the remit or concern of such a protocol what happens to any data 
> it carries after it has been transferred.

At least that's not the case for HTTP, which specifies, for instance,
the semantics of (client-side) caching.  If that was not so, the *WWW*
would be an even greater mess as it is.

Consider the given survey form would be submitted via a GET request.
Anybody requesting the very URI again, would cause the same record to be
appended to the file another time.  This could even be the original
submitter, pressing F5 inadvertently -- a former POST submission would
have triggered a warning in any contemporary browser.[1]  Furthermore
the original submitter might bookmark the current URI after form
submission -- consider what happens when she accesses the bookmark next
time.[2]  Consider what happens if this URI is shared on a social
network, for instance.

> That you can't spot this flaw in the document you're quoting speaks 
> volumes for your knowledge of the internet.

Ex falso quodlibet.

[1] I am aware that multiple submission of the same data are still
possible with a POST request without warning, though.
[2] I am also aware that there are workarounds to prevent storing the
data twice, but these are unreliable and merely try to work around the
HTTP specification.

-- 
Christoph M. Becker

Back to comp.lang.php | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Newby neds help F. George McDuffee <gmcduffee@mcduffee-associates.us> - 2015-02-07 14:38 -0600
  Re: Newby neds help Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-02-07 16:31 -0500
  Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-07 23:30 +0100
  Re: Newby neds help Tim Streater <timstreater@greenbee.net> - 2015-02-07 22:36 +0000
  Re: Newby neds help Denis McMahon <denismfmcmahon@gmail.com> - 2015-02-08 00:06 +0000
    Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-08 01:29 +0100
      Re: Newby neds help Jerry Stuckle <jstucklex@attglobal.net> - 2015-02-07 20:22 -0500
        Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-08 02:33 +0100
          Re: Newby neds help Jerry Stuckle <jstucklex@attglobal.net> - 2015-02-07 20:54 -0500
      Re: Newby neds help Denis McMahon <denismfmcmahon@gmail.com> - 2015-02-08 13:27 +0000
        Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-08 15:22 +0100
          Re: Newby neds help Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-02-08 21:58 +0100
            Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-08 22:56 +0100
              Re: Newby neds help Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-02-08 23:36 +0100
                Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-09 00:14 +0100
                Re: Newby neds help Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-02-09 00:42 +0100
                Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-09 00:58 +0100
                Re: Newby neds help Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-02-09 00:30 +0100
                Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-10 00:53 +0100
          Re: Newby neds help Denis McMahon <denismfmcmahon@gmail.com> - 2015-02-08 21:46 +0000
            Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-09 00:40 +0100
              Re: Newby neds help Denis McMahon <denismfmcmahon@gmail.com> - 2015-02-09 19:34 +0000
                HTTP (was: Newby neds help) "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-10 02:04 +0100
        Re: Newby neds help F. George McDuffee <gmcduffee@mcduffee-associates.us> - 2015-02-08 20:06 -0600
          Re: Newby neds help Matthew Carter <m@ahungry.com> - 2015-02-08 21:55 -0500
            Re: Newby neds help F. George McDuffee <gmcduffee@mcduffee-associates.us> - 2015-02-09 00:13 -0600
          Re: Newby neds help Tim Streater <timstreater@greenbee.net> - 2015-02-09 09:46 +0000
          Re: Newby neds help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-10 01:14 +0100
    Re: Newby needs help F. George McDuffee <gmcduffee@mcduffee-associates.us> - 2015-02-07 19:29 -0600
      Re: Newby needs help "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-08 02:40 +0100
      Re: Newby needs help Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-02-07 21:36 -0500
  Re: Newby neds help Jerry Stuckle <jstucklex@attglobal.net> - 2015-02-07 21:33 -0500
  Re: Newby neds help Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-02-09 20:02 -0500

csiph-web