Content Negotiation — Aquilia Documentation
Comprehensive guide and documentation for Content Negotiation in the Aquilia framework. View API reference, examples, and implementation patterns.
Controllers Content Negotiation & Renderers Aquilia handles content negotiation dynamically by parsing the client's Accept header quality factors and dispatching response payloads to pluggable renderers. Built-in Renderers Aquilia ships with a suite of highly-optimized, format-specific renderers: Renderer Class Media Type Format Suffix Config Options , , , , , ].map((row, i) => ( ))} Declaring Renderers Renderers are registered on a Controller class or overridden for individual route handlers: Authoring Custom Renderers To build a custom format serializer, subclass BaseRenderer and implement the render method: Negotiation Resolution Order Query parameter override: e.g., ?format=xml or ?format=yaml Accept Header quality factors: Parsed quality parameters (e.g. Accept: application/xml;q=0.9, application/json;q=0.8) Default: Resolves to the first renderer defined in renderer_classes (typically JSON) Controllers Overview )
Go to Homepage