Opened 4 years ago

Closed 3 years ago

#1117 closed enhancement (fixed)

ngx_http_v2_module documentation says HTTP/2 is experimental

Reported by: Jacques Chester Owned by:
Priority: minor Milestone:
Component: documentation Version: 1.9.x
Keywords: http/2 Cc:
uname -a:
nginx -V: 1.11.5

Description

Specifically: "The module is experimental, caveat emptor applies."

This module has been shipping in mainline and stable for some time. It's unclear if the warning, which was given at 1.9.5, still applies.

This question is blocking Cloud Foundry Buildpacks team from enabling HTTP/2 in the Nginx binaries we build for downstream consumers: https://github.com/cloudfoundry/staticfile-buildpack/issues/81

Change History (4)

comment:1 by Jacques Chester, 4 years ago

Sorry, should've filed against version 1.11.x.

We also build binaries for 1.10.x.

comment:2 by Maxim Dounin, 4 years ago

The HTTP/2 protocol is new and known to have various implementation and interoperability problems. And nginx implementation is as well new and have bugs. This clause exists for a reason: to warn server administrators who enable HTTP/2 that they have to be prepared to face bugs and interoperability problems.

On the other hand, just compiling HTTP/2 module have a minimal effect on nginx, and this is expected to be perfectly safe. Our own packages are compiled with HTTP/2.

in reply to:  2 comment:3 by Jacques Chester, 4 years ago

Sorry for the slow reply, I didn't realise Trac hadn't collected my email address from Google during login.

Replying to mdounin:

The HTTP/2 protocol is new and known to have various implementation and interoperability problems. And nginx implementation is as well new and have bugs. This clause exists for a reason: to warn server administrators who enable HTTP/2 that they have to be prepared to face bugs and interoperability problems.

I see. However, the sentence says "The module is experimental", not "The HTTP/2 protocol is experimental".

On the other hand, just compiling HTTP/2 module have a minimal effect on nginx, and this is expected to be perfectly safe. Our own packages are compiled with HTTP/2.

Yes, we noticed that when we dug a bit more, which is why we filed this bug. We're happy to follow your example if you feel the module is production-ready, but still recommend that the documentation be updated.

comment:4 by maxim, 3 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.