/ 
PAGI-Server-0.002012

Changes for version 0.002012 - 2026-09-01

  • Conformance
  • Implements PAGI 0.002008 (Www sub-spec 0.5). HTTP, WebSocket and SSE scopes now report spec_version 0.5; the lifespan sub-spec is unchanged at 0.3.
  • A response body is either inline http.response.body events or a single file/fh event, never both. Sending file or fh after inline body bytes now fails that send's Future. The failed send delivers no bytes and leaves the response sequence state untouched, so an application may still recover by finishing inline.
  • What may break
  • An application that prepended inline bytes to a file/fh body -- a generated header row ahead of a delegated export, say -- will see that send fail. Send the whole body inline instead, or put the leading bytes in the file. This is the rule that keeps a compressing intermediary from emitting a response whose declared encoding does not describe its bytes.
  • Tests asserting spec_version eq '0.4' on an http, websocket or sse scope need updating to '0.5'.

Documentation

README.md
SECURITY.md
pagi-server
PAGI application server
PAGI::Server::Compliance
HTTP/1.1, HTTP/2, WebSocket, SSE, and Security Compliance Documentation

Modules

PAGI::Server
PAGI Reference Server Implementation
PAGI::Server::AppNormalizer
Normalizes PAGI 0.4 application providers to a coderef
PAGI::Server::AsyncFile
Non-blocking file I/O for PAGI::Server internals
PAGI::Server::Connection
Per-connection state machine
PAGI::Server::ConnectionState
Connection state tracking for HTTP requests
PAGI::Server::EventValidator
Mandatory outgoing-event validation
PAGI::Server::Protocol::HTTP1
HTTP/1.1 protocol handler
PAGI::Server::Protocol::HTTP2
HTTP/2 protocol handler using nghttp2
PAGI::Server::Runner
PAGI application loader and server runner
PAGI::Server::TransportState
Outbound flow-control introspection for a connection

Provides

PAGI::Server::Protocol::HTTP2::Session
in lib/PAGI/Server/Protocol/HTTP2.pm

Examples

Other files