Re: HTTP/2 Upgrade with content?

On Fri, Mar 13, 2015 at 11:43:11PM +1300, Amos Jeffries wrote:
> 
> No matter what you do the client has started sending a request specifid
> as having a payload in HTTP/1 format. It must finish that request,
> including the payload it promised, before any HTTP/2 may happen.
>  - if the client is smart it would use chunked encoding then abandon
> with 0-sized chunk on seeing the 30x. But that has other nasty problems,
> and servers cant rely on it.

Sigh.

And if the client did 100-Continue, starts sending and gets 307, there
is real risk that client has no choice but treat that as a fatal error
(will not retry, report failure back to user/caller).

> We have some prior painful experience applicable from NTLM vs POST
> requests. In all cases there is large bandwidth wastage and latency.
 
And in some cases, things just plain won't work...


-Ilari