- From: Michael Sweet <msweet@apple.com>
- Date: Wed, 29 Apr 2015 12:52:15 -0700
- To: Zhong Yu <zhong.j.yu@gmail.com>
- Cc: "henry.story@bblfish.net" <henry.story@bblfish.net>, Willy Tarreau <w@1wt.eu>, Eric Covener <covener@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
If "global" scope on servers (or the web, depending on the server) is OK, would defining a well-known URI path be useful here? E.g., "GET /.wellknown/search?q=string"? > On Apr 29, 2015, at 10:12 AM, Zhong Yu <zhong.j.yu@gmail.com> wrote: > > On Wed, Apr 29, 2015 at 11:53 AM, henry.story@bblfish.net > <henry.story@bblfish.net> wrote: > >> But hey if you and everybody else here thinks that deployment is the only >> issue left here, then that would be good to know. :-) > > It appears to me that the only problem SEARCH solves(or rather, > avoids) is the limitation of URI length. That *is* a deployment issue. > > So GET is fine, it's just constrained by the current deployments for > your use cases. You want a workaround, which, nevertheless, works > through *the current deployment*. > > Zhong Yu > bayou.io _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair
Received on Wednesday, 29 April 2015 19:52:44 UTC