/ 
PAGI-0.002012

Changes for version 0.002012 - 2026-10-01

  • Specification
    • Clarify path, raw_path and root_path (Www 0.6). root_path followed by path is the path the client requested: whatever sets or extends root_path removes that prefix from path (PSGI's SCRIPT_NAME/PATH_INFO model; PAGI deliberately differs from ASGI, where path includes root_path). raw_path is the full requested path, percent-encoded, at every level: mounts leave it, a server root path is prepended. New section "Paths, Mounts and Root Paths": whole-segment prefixes, never strip a root path "only if present", root_path shape and trust, leading "//", and never authorize on raw_path. SSE scopes list raw_path, query_string and root_path among the keys they reuse. The PSGI mapping said PATH_INFO is "path minus root_path"; it is path, and REQUEST_URI is raw_path plus the query.

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
PAGI::Upgrading
What changed between sub-spec versions, and what to do about it

Modules

PAGI
Perl Asynchronous Gateway Interface

Examples

Other files