W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2018

Re: GET/POST parameters question

From: Willy Tarreau <w@1wt.eu>
Date: Mon, 11 Jun 2018 23:20:57 +0200
To: "Roy T. Fielding" <fielding@gbiv.com>
Cc: Grahame Grieve <grahame@healthintersections.com.au>, ietf-http-wg@w3.org
Message-ID: <20180611212057.GA2779@1wt.eu>
On Mon, Jun 11, 2018 at 02:05:00PM -0700, Roy T. Fielding wrote:
> Presumably, an application will use parameters when
> and where desired. If not desired, a 404 error is a normal response.

Several years ago for an application I was working on, I explicitly
wanted to support both url-params and body for POST requests because
for me they are completely different and orthogonal beasts. But I
found that it doesn't cope well with a number of application frameworks
which are confused because (probably due to inheritance of the old days
of CGI), for them a parameter is a parameter, wherever it's found, so
these were completely mixed at various places in the chain. Thus I
gave up, a bit sadly, considering that I was prevented from doing it
just due to the risk of poor interoperability at some places and not
for any technical reason.

Received on Monday, 11 June 2018 21:21:28 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:59 UTC