Commits
Tarun Sukhani authored 11cf18f71ff
docs: README rewrite — drop nonexistent http2/http3 enable flags
The README documented three properties that don't exist in code:
play.http2.enabled, play.http3.enabled, and play.http3.port. Both
protocols are now implicitly active whenever HTTPS is configured —
h2 is always advertised via ALPN (SslHttpServerPipelineFactory.java
hardcodes ALPN_PROTOCOLS = {"h2", "http/1.1"}), and h3 binds a UDP
listener on the same port number as the TCP HTTPS port whenever
native QUIC is available (Server.java:168, with the comment "no
separate play.http3.enabled flag"). On platforms without native
QUIC the framework logs WARN and continues with TCP-only — the
README's "refuses to start" claim was inverted.
Two "Enabling HTTP/2" and "Enabling HTTP/3" sections merged into
one "TLS, HTTP/2, and HTTP/3" section that reflects the unified
configuration: bind https.port + provide a PEM cert+key, and all
three protocols activate together. Curl examples standardized on
port 9443 (matches the play enable-https default).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>