- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 28 Apr 2015 20:57:55 +0200
- To: "Roy T. Fielding" <fielding@gbiv.com>
- CC: "henry.story@bblfish.net" <henry.story@bblfish.net>, ashok malhotra <ashok.malhotra@oracle.com>, Mark Nottingham <mnot@mnot.net>, James Snell <jasnell@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2015-04-28 18:29, Roy T. Fielding wrote: > ... > That is scoping by the message body, not by the method semantics. The difference is Yes. > that the request target contains essential bits for routing a request within (or behind) > the origin server, so if a special route is applied to, for example, a path within the > URI, then we want the method semantics to be limited to the scope of that path. > If the scope is not limited by the method, then implementation gets very messy. > [POST might have remained limited in that way as well, but the introduction of forms > made its original semantics irrelevant, so there wasn't much point in scoping them.] I agree with the explanation, but exactly how is this different from how a GET on a search engine works? > ... Best regards, Julian
Received on Tuesday, 28 April 2015 18:58:35 UTC