Sorry for the late response. I see the check was changed to fsockopen("localhost") (instead of trying for /serverpush). If there's a local server running the test will attempt to run as well. If there's a problem with testing for /serverpush an env variable might be better after all. Sorry for the back and forth.

The main problem is that file_get_contents doesn't have support for TLS (and so HTTS) by default, at least on my machine.

That's why I used fsockopen instead.

I could try to use curl instead of file_get_contents, but the check will take more lines of code.

I guess that could be moved to a shared skipif file if too long. If it doesn't work well I won't object to a env var.

@iluuu1994 is there anything more to do on this patch?

Fwiw, most browsers and servers drop support for http2 server push.

Not sure whether keeping it in php is the right direction

See e.g.

• https://twitter.com/nginxorg/status/1668741255549911040

• https://developer.chrome.com/blog/removing-push/

I am no expert, just mention what I found by accident

Indeed Chrome recommends 103 Early Hints (status in PHP: #7025) now, but Server Push is still supported by many tools (server-side and client-side) and will not be removed from the spec.

Anyway, enabling these tests is not related to the status of Server Push. As long as the code is part of PHP (and of curl) and officially supported, it should be tested.

If we (or curl) remove this feature at some point, then we'll remove the corresponding tests.

Segfaults have been fixed in libcurl 8.1.0. I skipped these tests if libcurl version is older.

At last 😄 Thanks @dunglas!