- From: Willy Tarreau <w@1wt.eu>
- Date: Wed, 29 Apr 2015 09:01:41 +0200
- To: Julian Reschke <julian.reschke@greenbytes.de>
- Cc: "henry.story@bblfish.net" <henry.story@bblfish.net>, HTTP Working Group <ietf-http-wg@w3.org>
Hi Julian, On Wed, Apr 29, 2015 at 08:36:02AM +0200, Julian Reschke wrote: > >>$ telnet bblfish.net 80 > >>Trying 208.64.60.175... > >>Connected to bblfish.net. > >>Escape character is '^]'. > >>GET / HTTP/1.1 > >>Host: bblfish.net > >>Content-Type: text/query > >>Accept: text/csv > >>Content-Length: 42 > >> > >>select surname, givenname, email limit 10 > > > >Why not use POST then ? Passing a body in GET could confuse caches and > >result in wrong data being retrieved. There are reasons why POST is a > >different method. > > That rational also needs to be in the spec (for instance: SEARCH is > safe, POST is not). Yes good point. My argument was in fact against the misuse of GET but you're right, let's be precise :-) Cheers, Willy
Received on Wednesday, 29 April 2015 07:02:12 UTC