Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90003
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 74.125.82.42 cause and error)
MIME-Version: 1.0
Sender: me@daveyshafik.com
In-Reply-To: <C8.26.07292.AD8AA865@pb1.pair.com>
References: <CANaX5nerE2XAHmgiync0QDqGB6qf6_SfT0SP=A+dw7d8Pt4=yw@mail.gmail.com>
	<C8.26.07292.AD8AA865@pb1.pair.com>
Date: Mon, 4 Jan 2016 20:44:54 +0000
Message-ID: <CANaX5ncMVWOZ+H5xqgLF2i2kyrKm3=YHzTkQozax7qnU40dSfQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114b15dc83fd3d0528883182
Subject: Re: [PHP-DEV] Re: Testing HTTP/2 support in PHP
From: davey@php.net (Davey Shafik)

--001a114b15dc83fd3d0528883182
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Andrea

On Mon, Jan 4, 2016 at 5:16 PM, Andrea Faulds <ajf@ajf.me> wrote:

> Hi Davey,
>
> Davey Shafik wrote

[snip]

We could also add a flag (e.g. --[no-]http2) on the CLI for
>> enabling/disabling it =E2=80=94 this would be helpful for testing HTTP/2=
 client
>> fallback when it's not supported.
>>
>
> Hmm, this would mean a new dependency, and more potential complexity. I'm
> not sure if HTTP/2 justifies it.
>

This is the main reason I think it should be optional. But I do think
HTTP/2 justifies it none-the-less. HTTP/2 has the potential to completely
disrupt our HTTP architecture =E2=80=94 it removes the need for things like=
 JS/CSS
inlining, JS/CSS minifying, CSS image sprites, domain sharding, and more.


> Also, don't all the major client implementations of HTTP/2 require TLS? O=
r
> is localhost given a free pass?


All browser implementations do require TLS, most other clients do not.
Given that cli-server is intended for development only so shipping some
"self" signed certs might be fine. I'd suggest integrating with letsencrypt
but they can't issue certs for localhost (no public CA can).


> This is a much more useful tool than relying on node for make tests, and
>> allows us to test adding HTTP/2 support to ext/curl, the HTTP stream
>> (which
>> could also use libnghttp2=E2=80=A6), userland HTTP/2 clients, pecl_http =
(if that's
>> still a thing), etc.
>>
>
> If added, I suppose it would be useful for PHP developers testing HTTP/2
> features like Server Push, assuming the CLI server supported it.
>

If we use nghttp2 it should.

Thanks,

- Davey

--001a114b15dc83fd3d0528883182--