Angel
Search…
Primary version
Introduction
Migration from Angel 1.1.x
ORM
Guides
Getting Started
Basic Routing
Dependency Injection Patterns
Installation & Setup
Without the Boilerplate
Requests & Responses
Dependency Injection
Basic Routing
Request Lifecycle
Middleware
Controllers
Parsing Request Bodies
Using Plug-ins
Rendering Views
Service Basics
REST Client
Testing
Error Handling
Pattern Matching and Parameter
Command Line
Writing a Plugin
Example Projects
YouTube Tutorials
Ecosystem
Packages
Powered By GitBook
Request Lifecycle
Requests in the Angel framework go through a relatively complex lifecycle, and to truly master the framework, one must understand that lifecycle.
  1. 1.
    startServer is called.
  2. 2.
    Each HttpRequest is sent through handleRequest.
  3. 3.
    handleRequest converts the HttpRequest to a RequestContext, and converts its HttpResponse into a ResponseContext.
  4. 4.
    angel_route is used to match the request path to a list of request handlers.
  5. 5.
    Each handler is executed.
  6. 6.
    If the response is using streaming, and not buffering content, skip to step 8 (default).
  7. 7.
    All responseFinalizers are run.
  8. 8.
    If res.isDetached == false, all headers, the status code and the response buffer are sent through the actual HttpResponse.
  9. 9.
    The HttpResponse is closed.
If at any point an error occurs, Angel will catch it. See the error handling docs for more.
Previous
Basic Routing
Next
Middleware
Last modified 3yr ago
Copy link