http3: explain how to enable qlog for HTTP/3 events

[Copilot]

HTTP/3 qlogging was added in v0.56.0 but remained undocumented.

Changes

• New documentation page (content/docs/http3/qlog.md) covering:

  • Enabling qlogging via http3/qlog.DefaultConnectionTracer
  • Server and client configuration examples
  • Custom tracer implementation with both QUIC and HTTP/3 event schemas
  • HTTP/3 events: frame_created, frame_parsed, datagram_created, datagram_parsed

• Removed outdated references:

  • "Future Work" note about HTTP/3 qlog support from client.md
  • "Future Work" section from quic/qlog.md

Usage

import h3qlog "github.com/quic-go/quic-go/http3/qlog"

server := http3.Server{
	QUICConfig: &quic.Config{
		Tracer: h3qlog.DefaultConnectionTracer,
	},
}

The tracer automatically includes both QUIC and HTTP/3 event schemas, writing to $QLOGDIR if set.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• cdn.jsdelivr.net
  • Triggering command: /usr/local/bin/hugo hugo --minify /home/REDACTED/.lohttp3.*qlog\|qlog.*http3 grep -l g.*http3 streams_blocked_frame_test.go nfig/composer/vendor/bin/grep g.*http3 ket.go ndor/bin/grep grep -l g.*http3 ./internal/wire/retire_connection_id_frame.go /opt/pipx_bin/grep g.*http3 o ep grep (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>http3: explain how to enable qlogging</issue_title>
<issue_description>This was added in v0.56.0, but we haven't updated the documentation yet.</issue_description>

<agent_instructions>This should create a new site in the HTTP/3 section. Make sure to look up the quic-go API for how it's done. It might be instructive to look at the quic-go integration tests.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes http3: explain how to enable qlogging #118

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR adds documentation for HTTP/3 qlog support that was introduced in v0.56.0 but remained undocumented. The documentation explains how to enable HTTP/3 event logging alongside QUIC event logging using the http3/qlog package.

Key Changes:

• New documentation page for HTTP/3 qlog functionality with configuration examples
• Removed outdated "Future Work" references to HTTP/3 qlog support from existing documentation

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
content/docs/http3/qlog.md	New documentation page explaining how to enable HTTP/3 qlogging using http3/qlog.DefaultConnectionTracer, including code examples and cross-references to QUIC qlog documentation
content/docs/quic/qlog.md	Removed "Future Work" section mentioning HTTP/3 qlog support since it's now implemented
content/docs/http3/client.md	Removed qlog support item from Future Work list since it's now available

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.