Order of Operations

Custom event hooks

This list shows the order in which any user-defined custom hooks are executed:

1. EndpointHostConfig.RawHttpHandlers are executed before anything else, i.e. returning any ASP.NET IHttpHandler by-passes ServiceStack completely and processes your custom IHttpHandler instead.
2. If the Request doesn't match any existing Routes it will search IAppHost.CatchAllHandlers for a match
3. The IAppHost.PreRequestFilters gets executed before the Request DTO is deserialized
4. Default Request DTO Binding or Custom Request Binding (if registered)
5. Request Filter Attributes with Priority < 0 gets executed
6. Then any Global Request Filters get executed
7. Followed by Request Filter Attributes with Priority >= 0
8. Action Request Filters (New API only)
9. Then your Service is executed with the configured IServiceRunner and its OnBeforeExecute, OnAfterExecute and HandleException custom hooks are fired
10. Action Response Filters (New API only)
11. Followed by Response Filter Attributes with Priority < 0
12. Then Global Response Filters
13. Followed by Response Filter Attributes with Priority >= 0
14. Finally at the end of the Request IAppHost.OnEndRequest is fired

Any time you close the Response in any of your filters, i.e. httpRes.EndServiceStackRequest() the processing of the response is short-circuited and no further processing is done on that request.

Implementation architecture diagram

The Implementation architecture diagram shows a visual cue of the internal order of operations that happens in ServiceStack:

After the IHttpHandler is returned, it gets executed with the current ASP.NET or HttpListener request wrapped in a common IHttpRequest instance.

The implementation of RestHandler shows what happens during a typical ServiceStack request: