Re: POST oddness

[John R. <Joh...@as...>]

hmmmmm,

That may be all and well, but that append seems to be corrupting the in hash.
However I spotted that I have not updated minserv.pl and that POSTed data is
being manipulated in there. I will have to update and have a poke around.

John

Jamie Cameron wrote:

> "Ryan W. Maple" wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Thu, 8 Feb 2001, Jamie Cameron wrote:
> >
> > > That's pretty much correct - the code is designed to handle the case
> > > where a request has both GET and POST data. The request method may
> > > be POST, but the URL includes ?foo=bar&smeg=spod parameters as well ..
> >
> > Is that even possible?  I thought a request could only do GET _or_ POST
> > since the request line is only one line.
> >
> > - From the HTTP 1.1 specification [1]:
> >
> >        Method         = "OPTIONS"                ; Section 8.1
> >                       | "GET"                    ; Section 8.2
> >                       | "HEAD"                   ; Section 8.3
> >                       | "POST"                   ; Section 8.4
> >                       | "PUT"                    ; Section 8.5
> >                       | "PATCH"                  ; Section 8.6
> >                       | "COPY"                   ; Section 8.7
> >                       | "MOVE"                   ; Section 8.8
> >                       | "DELETE"                 ; Section 8.9
> >                       | "LINK"                   ; Section 8.10
> >                       | "UNLINK"                 ; Section 8.11
> >                       | "TRACE"                  ; Section 8.12
> >                       | "WRAPPED"                ; Section 8.13
> >                       | extension-method
> >
> > So I guess I'm saying, is this even necessary (especially if it's breaking
> > in the case cited)?
>
> That code is only really used when a request is POST, but also contains
> GET-style parameters in the URL. For example, if you had a form like
>
> <form method=post action='foo.cgi?bar=1'>
> <input name=smeg value='2'>
> </form>
>
> In this case, webmin would pick up both the bar and smeg parameters.
> There was some good reason for including this feature, but I can't
> remember it now :)  However, it doesn't really cause any harm as 99%
> of all forms will have either GET or POST parameters only.
>
>  - Jamie
>
> -
> Forwarded by the Webmin development list at web...@we...
> To remove yourself from this list, go to
> http://lists.sourceforge.net/lists/listinfo/webadmin-devel