forked from NancyFx/Nancy
-
Notifications
You must be signed in to change notification settings - Fork 0
Implementing a host
thecodejunkie edited this page Oct 19, 2011
·
1 revision
This page contains implementation advice for view engines. It's work-in-progress
- The url of a Nancy request should always be url-decoded
- The query-string of a Nancy request should always be url-encoded
- Should set Content-Type of response sent by the host
- Should set Status of the response sent by the host
- Should set all cookies of the response sent by the host
- Should set all headers of the response sent by the host
- Taking a look at the DynamicDictionary
- The before and after module hooks
- Model binding
- Bootstrapper
- View Engines
- View location conventions
- Testing your application
- The root path
- Managing static content
- Diagnostics
- Adding a custom FavIcon
- The Application Before, After and OnError pipelines
- Generating a custom error page
- The cryptography helpers
- Content negotiation
- Authentication
- More to come
- Hosting Nancy with ASP.NET
- Hosting Nancy with WCF
- Hosting Nancy with Azure
- Hosting Nancy with OWIN
- Hosting Nancy with Umbraco
- Hosting Nancy with Nginx on Ubuntu
- Self Hosting Nancy
- Implementing a Host
- Accessing the client certificate when using SSL
- Blog Posts, Video & Audio
- Async-Beta (Async Beta)