On Mon, Dec 7, 2015 at 4:12 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
> On Mon, Dec 7, 2015 at 2:39 PM, Stefan Eissing < > stefan.eiss...@greenbytes.de> wrote: > >> There can be no 100 after a 101. After a 101, the downstream speaks the >> new protocol, immediately. >> > > Right, and the new protocol is TLS/1.x HTTP/1.1 in the mod_ssl case. > What's > so confusing? > And in that case, define 'immediately' :) That's where the RFC2817 ambiguity came in, 100 before/after 101, which was then resolved by RFC7230 as noted earlier (but not in the manner one at least I might have hoped for).
