Re: Expect: + Upgrade: = ...

That would be potentially problematic in some ways, as you really do want
to be in the http/2 context for the response.
We could solve some of this by stating that you must not have expect:
continue when upgrading to http/2.

-=R


On Thu, Sep 5, 2013 at 1:30 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 5 September 2013 11:17, Roy T. Fielding <fielding@gbiv.com> wrote:
> >
> > Using both Expect: 100-continue and Upgrade, at the same time,
> > will work fine -- it can be implemented as already specified.
> > 100 is required to be sent first.
>
> Reading
> http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-23#section-6.7,
> this wasn't obvious, should it be?
>
> No question that it is the right thing to do: complete the HTTP/1.1
> request before proceeding with the next protocol; otherwise the client
> side of the connection is in an indeterminate state.  (It needn't be,
> but the alternative would depend on 100-continue being consistently
> implemented, and we know that hasn't happened.)
>
>