Re: POST oddness

[Ryan W. M. <ry...@gu...>]

-----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)?

Cheers,
Ryan

[1] http://www.w3.org/Protocols/HTTP/1.1/spec.html#Method

 +-- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --+
   Ryan W. Maple          "I dunno, I dream in Perl sometimes..."  -LW
   Guardian Digital, Inc.                     ry...@gu...
 +-- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --+

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6gcIPIwAIA9MpKWcRAsNEAJ9k5q48xVd1rM9hMSeqX47D/QlJHgCdH3jO
IqgvBs9evU3JgSOJjmWDGfQ=
=NZ+r
-----END PGP SIGNATURE-----