- From: Grahame Grieve <grahame@healthintersections.com.au>
- Date: Tue, 12 Jun 2018 08:49:20 +1000
- To: Willy Tarreau <w@1wt.eu>
- Cc: "Roy T. Fielding" <fielding@gbiv.com>, ietf-http-wg@w3.org
Received on Monday, 11 June 2018 22:49:45 UTC
thank you both Grahame On Tue, Jun 12, 2018 at 7:20 AM, Willy Tarreau <w@1wt.eu> wrote: > 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. > > Cheers, > Willy > -- ----- http://www.healthintersections.com.au / grahame@healthintersections.com.au / +61 411 867 065
Received on Monday, 11 June 2018 22:49:45 UTC