- From: Zhong Yu <zhong.j.yu@gmail.com>
- Date: Tue, 22 Jul 2014 18:13:18 -0500
- To: Greg Wilkins <gregw@intalio.com>
- Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On Tue, Jul 22, 2014 at 5:38 PM, Greg Wilkins <gregw@intalio.com> wrote: > > On 22 July 2014 16:16, Zhong Yu <zhong.j.yu@gmail.com> wrote: >> >> > The semantic that the client application is seeking is confirmation from >> > the >> > origin server that it has inspected the headers and has consented for >> > the >> > body to be sent. >> >> This is a new way of interpreting it, but it's probably not the >> original intent, and it's not supported by the text of the spec. If a >> server does not respond with 100, it doesn't mean the body is >> forbidden to be sent; the client can always send the body regardless >> of server response(s). > > > Consent to send != permission to send. > > Clients can always just send the body, but 100 continues allows them the ask > the application on the server if it is OK to send the body. The > important part of this is that the question is asked of the application and > not of the transport. It is not asking "can I send the body?", it is > asking "should I send the body?". The key difference here is that the > first question can be answered by a proxy, while the second question is > fundamentally an end to end question. The question is more like, "is it OK if I do *not* send the body?". Only the origin server can give a "yes" answer to that, by sending a final response code which in itself is end-to-end. Even with the answer "yes, the body is not needed", the client can send the body regardless, therefore the answer is advisory, and it should have no impact on application semantics. Zhong Yu bayou.io > > cheers > > > > -- > Greg Wilkins <gregw@intalio.com> > http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales > http://www.webtide.com advice and support for jetty and cometd.
Received on Tuesday, 22 July 2014 23:13:46 UTC