http3 0.0.3

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7342e51b5150f53092806631b85d5d1053d16f7f757c26730227fd0a9d27619d
+  data.tar.gz: 7c7cee88475696117fcfe14e42333fc1267ffc0942c40360f6b6d0fcc9b487cf
+SHA512:
+  metadata.gz: 802c51e3f9040ac9d51ff0f6afee6e1541f7f479f94336283d49c346c127bf6740fca313ce4badb5627ba03e4793be9cd1536bafbfec24a180a3658a2a0c3cd7
+  data.tar.gz: fe45066ac7c54c622ff9c5fdab9d1fbc474867ce2076db6fd28f1c78ca4f65db8c5fbf1059b2dead1234e414902f8d43aa53c9912a08602fd0849425a5bfc480

data/.clang-format

@@ -0,0 +1 @@
+BasedOnStyle: LLVM

data/.vscode/extensions.json

@@ -0,0 +1,6 @@
+{
+    "recommendations": [
+        "ms-vscode.cpptools",
+        "shopify.ruby-lsp",
+    ]
+}

data/.vscode/settings.json

@@ -0,0 +1,10 @@
+{
+    "[c][cpp]": {
+        "editor.formatOnSave": true,
+        "editor.defaultFormatter": "ms-vscode.cpptools"
+    },
+    "[json][jsonc]": {
+        "editor.formatOnSave": true,
+        "editor.defaultFormatter": "vscode.json-language-features"
+    }
+}

data/CHANGELOG.md

@@ -0,0 +1,34 @@
+## [0.0.3] - 2026-10-13
+
+### Added
+- `HTTP3::Server` serves a Rack 3 application over HTTP/3 on one UDP address: `HTTP3::Server.new(app:, bind:, certificate_path:, private_key_path:, **options).run`. Options: `transport_params`, `settings`, `qlog_dir`, `max_connections` (1024), `max_request_body` (1 MiB, 413 beyond), `max_field_section_size` (64 KiB, 431 beyond), `send_buffer_size` (64 KiB), `shutdown_timeout` (30 s) and `logger`. SIGTERM or SIGINT sends GOAWAY, refuses new connections and waits for the requests under way (a second signal stops waiting); SIGHUP reloads the certificate and key for new connections. Only failures are logged, as `event key=value ...` lines without query strings or header values. Response bodies may be files (`to_path`, read 16 KiB at a time), arrays (`to_ary`) or anything with `each`; streaming bodies (`call`) are answered with 500. Request fields whose names contain `_` are left out of the Rack env, so that they cannot pass for the dashed name (`x_forwarded_for` for `x-forwarded-for`). A response whose field names are not lowercase tokens, or whose field values contain NUL, CR or LF, is answered with 500. ([#5](https://github.com/unasuke/http3-ruby/pull/5))
+- `HTTP3::Session`, HTTP/3 on one `QUIC::Connection::Server` through the quic gem's C function table; `HTTP3::RackAdapter`; and `HTTP3::Request`, `HTTP3::Response` and `HTTP3::Body`, the data passed between them. ([#5](https://github.com/unasuke/http3-ruby/pull/5))
+- `HTTP3::Nghttp3::Connection#read_stream` takes `ts:`, the time in nanoseconds for nghttp3's rate limits (CLOCK_MONOTONIC by default), and now calls `nghttp3_conn_read_stream2`. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- `HTTP3::Nghttp3::Connection#shutdown_stream_read`, `#set_max_client_streams_bidi` and `#pending_data`. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- Tests of `HTTP3::RackAdapter`, of `HTTP3::Session` over a QUIC loopback connection, and of `HTTP3::Server` serving files and dynamic bodies and handling signals. An HTTP/3 interop check fetches from the server with curl in a container (`test/interop/curl.sh`), weekly in CI; `test/interop/README.md` describes the checks run by hand. ([#6](https://github.com/unasuke/http3-ruby/pull/6))
+- The README documents installing http3 and running a Rack application on it: a launch script reading `config.ru`, the options, signals, logging and qlog, which responses get 500, and the Alt-Svc a TCP server has to send for browsers to find HTTP/3. `LICENSE-DEPENDENCIES.txt` reproduces the license terms of nghttp3 and sfparse, which are linked statically. ([#7](https://github.com/unasuke/http3-ruby/pull/7))
+
+### Changed
+- The gem is now `http3` (`require "http3"`), and the top-level namespace is `HTTP3`. The nghttp3 bindings move from `Nghttp3` to `HTTP3::Nghttp3`. No `Nghttp3` alias is left behind. ([#3](https://github.com/unasuke/http3-ruby/pull/3))
+- nghttp3 is no longer taken from the system. Version 1.13.1 is downloaded and built at install time with mini_portile2 and linked statically, so `libnghttp3-dev` is no longer needed. http3.so exports only `Init_http3`; the nghttp3 symbols stay hidden. ([#3](https://github.com/unasuke/http3-ruby/pull/3))
+- Ruby 3.3 or later is required, and only Linux is supported. ([#3](https://github.com/unasuke/http3-ruby/pull/3))
+- http3 depends on the quic gem (`~> 0.0.3`) and, when loaded, looks up the C function table it publishes in `quic/ext.h`. A quic gem without a compatible table makes `require "http3"` raise `LoadError` naming the ABI version needed and the quic version found. ([#4](https://github.com/unasuke/http3-ruby/pull/4))
+
+### Removed
+- The Ruby helpers on the bindings (`Nghttp3::Client`, `Server`, `Request`, `Response`, `Headers` and `StreamManager`). `HTTP3::Server` replaces the server side; the client side lives on in the tests only. ([#5](https://github.com/unasuke/http3-ruby/pull/5))
+
+### Fixed
+- An exception raised by a callback block or a body block no longer unwinds through nghttp3's frames, which left nghttp3 in an inconsistent state. It is kept until nghttp3 returns and then raised from the method that called into it (`#read_stream`, `#writev_stream`, `#add_ack_offset`, ...). ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- Body Strings are let go once the peer has acknowledged them, and when their stream closes. Before, a connection kept every body it ever sent. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- A body String is copied and frozen when submitted, and pinned until acknowledged, so neither the application nor `GC.compact` can change the bytes nghttp3 still reads. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- `GC.compact` could move a connection while nghttp3 held its address for callbacks. nghttp3 now gets a pointer to the C struct instead. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- `Connection.client_new` and `.server_new` raise `TypeError` for callbacks that are not an `HTTP3::Nghttp3::Callbacks`, instead of crashing in the first callback. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+- The GC could crash collecting an `HTTP3::Nghttp3::QPACK::Decoder`: freeing its stream contexts walked a Hash the GC might already have freed, and read the contexts' addresses wrongly from it. ([#2](https://github.com/unasuke/http3-ruby/pull/2))
+
+## [0.0.2] - 2026-10-13
+
+- The last release as the `nghttp3` gem: its description says that the gem is no longer maintained. The code is that of 0.0.1.
+
+## [0.0.1] - 2026-01-31
+
+- Initial release, as the `nghttp3` gem

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/LICENSE-DEPENDENCIES.txt

@@ -0,0 +1,66 @@
+Licenses of bundled dependencies
+================================
+
+The http3 gem downloads nghttp3 at install time, builds it on the installing
+machine and links it into http3.so statically. It therefore redistributes no
+third-party binaries; the terms are reproduced below for reference. The
+QUIC layer comes from the quic gem, which carries its own
+LICENSE-DEPENDENCIES.txt. The http3 gem itself is MIT licensed; see
+LICENSE.txt.
+
+
+nghttp3 1.13.1 -- https://github.com/ngtcp2/nghttp3
+---------------------------------------------------
+
+The MIT License
+
+Copyright (c) 2019 nghttp3 contributors
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Some nghttp3 source files also carry "Copyright (c) ngtcp2 contributors" or
+"Copyright (c) nghttp2 contributors" notices, under the same terms.
+
+
+sfparse (bundled in nghttp3 1.13.1, lib/sfparse) -- https://github.com/ngtcp2/sfparse
+-------------------------------------------------------------------------------------
+
+The MIT License
+
+Copyright (c) 2023 sfparse contributors
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Yusuke Nakamura
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,127 @@
+# http3-ruby
+
+> [!CAUTION]
+> This gem is for experimental purposes only. Do not use it in production environments.
+
+> [!WARNING]
+> The code in this repository is almost entirely generated by Claude Code and reviewed by a human.
+
+`http3` serves Rack 3 applications over HTTP/3. It runs QUIC through the
+[quic gem](https://github.com/unasuke/quic-ruby) and HTTP/3 through
+[nghttp3](https://github.com/ngtcp2/nghttp3), which it builds from source and
+links in statically. The nghttp3 bindings are also there to use directly, as
+`HTTP3::Nghttp3`.
+
+## Installation
+
+Linux only, Ruby 3.3 or later. Like the quic gem, installing builds C code, so
+it needs a C compiler, pkg-config and the OpenSSL development package
+(`build-essential pkg-config libssl-dev` on Debian and Ubuntu).
+
+```bash
+bundle add http3
+```
+
+or, without Bundler:
+
+```bash
+gem install http3
+```
+
+## Usage
+
+There is no `rackup` handler or command; start the server from a script:
+
+```ruby
+# server.rb
+require "http3"
+require "rack"
+
+app = Rack::Builder.parse_file("config.ru")
+
+HTTP3::Server.new(
+  app: app,
+  bind: "192.0.2.1:443",
+  certificate_path: "/etc/tls/fullchain.pem",
+  private_key_path: "/etc/tls/privkey.pem"
+).run
+```
+
+`bind` is one address, `"host:port"` or `"[2001:db8::1]:443"`. It has to name
+the address to serve: `0.0.0.0` and `[::]` are refused. The certificate file
+is a PEM chain, leaf first, and the key a PEM key without passphrase.
+
+Other options, with their defaults:
+
+| Option | Default | |
+| --- | --- | --- |
+| `max_connections:` | `1024` | Connections at once; more are refused with CONNECTION_REFUSED |
+| `max_request_body:` | `1_048_576` | Bytes of request body; more gets 413 |
+| `max_field_section_size:` | `65_536` | Bytes of request headers (RFC 9114 §4.2.2); more gets 431 |
+| `send_buffer_size:` | `65_536` | Bytes of a response body queued but unsent per stream |
+| `shutdown_timeout:` | `30` | Seconds a graceful stop waits for the requests under way |
+| `qlog_dir:` | `nil` | Directory for one qlog file per connection |
+| `transport_params:` | `QUIC::TransportParams.default` | QUIC transport parameters |
+| `settings:` | `QUIC::Settings.default` | QUIC settings (the ALPN is always `h3`) |
+| `logger:` | `Logger.new($stderr)` | Where failures are logged |
+
+Response bodies may be files (`to_path`, sent 16 KiB at a time as the
+connection takes them), arrays or anything with `each`. Streaming bodies
+(`call`) are not supported and get 500, as do response headers whose names
+are not lowercase tokens or whose values contain NUL, CR or LF.
+
+### Signals
+
+- `SIGTERM` or `SIGINT` stops gracefully: every client gets GOAWAY, new
+  connections are refused, and the server waits up to `shutdown_timeout`
+  seconds for the requests under way before closing every connection. A
+  second signal stops the wait.
+- `SIGHUP` reads the certificate and key again; new connections use them,
+  existing ones keep theirs. If they cannot be loaded, the server keeps the
+  old ones and logs `tls_reload_failed`.
+
+### Logging and qlog
+
+Only failures are logged, one line each: the event, then `key=value` pairs.
+Query strings and header values never appear. There is no access log; add
+`Rack::CommonLogger` to your `config.ru` for one:
+
+```ruby
+use Rack::CommonLogger
+run MyApp
+```
+
+`qlog_dir:` writes `<qlog_dir>/<connection ID>.sqlog` for every connection,
+for tools such as [qvis](https://qvis.quictools.info/).
+
+### Browsers
+
+Browsers find HTTP/3 through an `Alt-Svc` header on an HTTP/1.1 or HTTP/2
+response from the same host, so a TCP server there has to send
+
+```
+alt-svc: h3=":443"
+```
+
+That is configured in that server (nginx, Puma, ...), not in this gem.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then,
+run `bundle exec rake` to build the extension, run the tests and lint. You can
+also run `bin/console` for an interactive prompt.
+
+`test/interop/` holds the checks against other HTTP/3 implementations (curl,
+h3i, quic-interop-runner, browsers); see its README.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/unasuke/http3-ruby. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/unasuke/http3-ruby/blob/main/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT). The licenses of the nghttp3 code built into it are in `LICENSE-DEPENDENCIES.txt`.
+
+## Code of Conduct
+
+Everyone interacting in the http3-ruby project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/unasuke/http3-ruby/blob/main/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,20 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "minitest/test_task"
+
+Minitest::TestTask.create
+
+require "standard/rake"
+
+require "rake/extensiontask"
+
+task build: :compile
+
+GEMSPEC = Gem::Specification.load("http3.gemspec")
+
+Rake::ExtensionTask.new("http3", GEMSPEC) do |ext|
+  ext.lib_dir = "lib/http3"
+end
+
+task default: %i[clobber compile test standard]

data/ext/http3/extconf.rb

@@ -0,0 +1,48 @@
+# frozen_string_literal: true
+
+require "mkmf"
+require "mini_portile2"
+
+# nghttp3 is downloaded and built at install time and linked statically, so
+# installing needs no system package and always gets this version.
+# nghttp3_conn_read_stream2 needs 1.12.0 or later. nghttp3 depends on nothing
+# but libc, so its version does not have to follow the quic gem's ngtcp2.
+NGHTTP3_VERSION = "1.13.1"
+NGHTTP3_SHA256 = "07160f28af3ddc3e8b95c8bbefe08c650e7cf303375141b6ca35cc89b319f70d"
+
+nghttp3 = MiniPortile.new("nghttp3", NGHTTP3_VERSION)
+nghttp3.files = [{
+  url: "https://github.com/ngtcp2/nghttp3/releases/download/v#{NGHTTP3_VERSION}/nghttp3-#{NGHTTP3_VERSION}.tar.gz",
+  sha256: NGHTTP3_SHA256
+}]
+# The release tarball ships configure, so no autotools are needed.
+nghttp3.configure_options = [
+  "--enable-lib-only",
+  "--disable-shared",
+  "--with-pic"
+]
+nghttp3.cook
+
+nghttp3.mkmf_config(static: "nghttp3")
+# Without it, nghttp3.h declares the functions for a shared library.
+append_cflags("-DNGHTTP3_STATICLIB")
+
+abort "nghttp3/nghttp3.h not found" unless have_header("nghttp3/nghttp3.h")
+abort "libnghttp3 not linkable" unless have_func("nghttp3_version", "nghttp3/nghttp3.h")
+
+# The quic gem's C function table, through which HTTP3::Session drives a
+# QUIC connection. The header ships in the quic gem; the table itself is
+# looked up at load time with rb_ext_resolve_symbol (Ruby 3.3 or later).
+require "quic/ext_include"
+append_cppflags("-I#{QUIC::EXT_INCLUDE_DIR}")
+abort "quic/ext.h not found (the quic gem 0.0.3 or later provides it)" unless have_header("quic/ext.h")
+abort "rb_ext_resolve_symbol not found (Ruby 3.3 or later is required)" unless
+  have_func("rb_ext_resolve_symbol", "ruby.h")
+
+# Makes all symbols private by default to avoid unintended conflict
+# with other gems. To explicitly export symbols you can use RUBY_FUNC_EXPORTED
+# selectively, or entirely remove this flag.
+append_cflags("-fvisibility=hidden")
+append_ldflags("-Wl,--exclude-libs,ALL") # Unexport symbols from the static nghttp3
+
+create_makefile("http3/http3")