/ 
PAGI-0.002004

Changes for version 0.002004 - 2026-08-25

  • Specification clarifications - resolved ambiguities
    • Connection-level headers: over HTTP/1.1, when an application response carries an Upgrade header (e.g. on a 426 Upgrade Required), the server must include 'upgrade' among the tokens of the Connection header it supplies, per RFC 9110's requirement on any Upgrade sender. The application never sends Connection: upgrade itself; the server completes the pair. Closes the conflict between the server-owns-connection-headers rule and RFC 9110's 426 requirements.
    • The incomplete-response definition now says explicitly that it covers an application Future that fails with an exception, not only one that resolves, after http.response.start and before the terminal event. No behavior change: the neighboring clauses already treat exceptions identically, and the reference server conforms both ways.

Documentation

CONTRIBUTING.md
README.md
SECURITY.md
PAGI::Building
building frameworks and toolkits on PAGI
PAGI::Cookbook
worked, runnable recipes for the PAGI protocol
PAGI::EventLoops
how PAGI stays loop-agnostic, how not to block, and how a server binds to an event loop
PAGI::PSGI
coming to PAGI from PSGI
PAGI::Spec
The base PAGI specification: application interface and core concepts
PAGI::Spec::Extensions
The PAGI server extension mechanism
PAGI::Spec::Lifespan
The PAGI Lifespan protocol for startup and shutdown events
PAGI::Spec::Server
PAGI server and application-runner integration guidance
PAGI::Spec::Tls
The PAGI TLS extension for reporting connection security in scope
PAGI::Spec::Www
PAGI message formats for HTTP, WebSocket, and SSE
PAGI::Tutorial
Learn the PAGI protocol for async Perl web applications

Modules

PAGI
Perl Asynchronous Gateway Interface

Examples

Other files