The context request stuff

Request method: GET
Request path: /
Request url:
Request query: Nancy.DynamicDictionary
Request headers: Nancy.RequestHeaders
Request body: Nancy.IO.RequestStream
Request userhostaddress:
Request cookies: System.Collections.Generic.Dictionary`2[System.String,System.String]
Request session: Nancy.Session.NullSessionProvider
Request files: System.Collections.Generic.List`1[Nancy.HttpFile]
Request form: Nancy.DynamicDictionary

The context response stuff

Response contenttype: text/html
Response statuscode: OK
Response cookies: System.Collections.Generic.List`1[Nancy.Cookies.INancyCookie]
Response headers: System.Collections.Generic.Dictionary`2[System.String,System.String]
Response contents: System.Action`1[System.IO.Stream]

The model stuff

The tag "[ERR!]" simply indicates that the defined view is being asked to display an element that
does not exist in the provided model data. For the most part in these examples it can be ignored.

Viewing output from model with name: "[ERR!]"

REST test: hello world (high scoring literal segments) >

REST test: hello someone (lower scoring literal and capture segments) >{yournamehere}

REST test: hello (capture segments to matching class) >{id}/{firstName}/{lastName}

REST test: return dummies list (class based list example & negotiates output using json or xml) >

REST test: return dummies model (class based model example & negotiates response inc json) >

..or take a look at NancyFX on github, defining routes and other documentation

..or jump on over to our triality gateway at