On Wed, Jan 6, 2016 at 10:29 AM Graham Dumpleton <graham.dumple...@gmail.com> wrote:
> > On 6 Jan 2016, at 12:13 AM, Benoit Chesneau <bchesn...@gmail.com> wrote: > > So for me what should be WSGI 2? WSGI 2 should add against WSGI 1 the > following: > > - tell to the application it is actually an HTTP2 request (maybe > populating a wsgi.http2 true env) > > > In CGI implementations you would for HTTP/1.1 already get: > > SERVER_PROTOCOL: 'HTTP/1.1’ > > Under HTTP/2 when I tested some time back, I recollect it came through as > one would assume would be expected: > > SERVER_PROTOCOL: ‘HTTP/2’ > > Is there any reason that this existing CGI variable wouldn’t be sufficient > for this purpose? > > Graham > True. I don't think there is a need for another env. The current way also work for the future :) - benoît
_______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: https://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
