- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 29 Apr 2015 08:02:51 +0200
- To: "Roy T. Fielding" <fielding@gbiv.com>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2015-04-28 22:52, Roy T. Fielding wrote: >> On Apr 28, 2015, at 11:57 AM, Julian Reschke <julian.reschke@gmx.de> wrote: >> >> 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? > > Because a GET has all of the information necessary to see the scope > within the request target. > > ....Roy Hm, no. Example: <https://www.google.de/search?q=site:ietf.org+roy> Best regards, Julian
Received on Wednesday, 29 April 2015 06:03:26 UTC