only doing setters because i think getters would be pretty confusing.

pretty new to me, but it’s basically the same as 204

purpose of this test is to explictly show how to send a 200 response
when a body is not expected...

.error() still works for compatibility, but it will be removed in the
future. closes #94

add keygrip support

this.originalUrl && this.request.originalUrl

just realized this since we removed the top closure. i'm not sure if
there's a better way to sol...

Expose proto

until we figure out a good way to return both weak and strong validators

response.etag and response.lastModified

need tests for this

Add/ctx request response

correct the link

specifically 3xx codes except for 304. closes #66

replace content-negotiation accessors with 0-arity method calls

less common than .auth which we removed as well but we can
add them back if it becomes a common ...

pass an optional `next` to app.callback()

i'm not sure if this is incorrect. people should use `accepts()`
anyways.

pretty annoying to continuously update these. we'll start pining them
when you can actually use ...

get away from promoting the extension of prototypes, aside
from it looking better there isnt rea...

bump node-methods

debug context: notify if a property is being overwritten

for node

i like keeping things as similar to node as possible :)

Update Readme.md

The request results in a resource being returned so 200 is more appropriate rather than 201 whic...

since it cant be anything else, but if you have middleware that transforms
the object to xml or ...

set length on body override

bind .onerror to context

onerror: check existence of error

this prevents a bunch of redundant checks that middleware may need to
check response length, typ...

Fixed typo

`ctx.accept` -> `ctx.accepts`

so you can easily unwind the stack for 404s