Default "not found" route.

[alganet]

I believe the Router should have a default route for not found routes.

[ramsey]

I agree. Either a default route, or return 404 Not Found by default, or do both.

[augustohp]

This could lead to a lot of Default routes to different error codes, could't it?!

[alganet]

Yep, I could think of 404 (for no matches on the router), 405 (which @ramsey mentioned in another issue), 406 for routes that do exist but doesn't map to any of the supported mime types declared in the Accept routine, 500 (for every PHP error or exception uncaught) and 505 (for crazy unsupported HTTP version headers).

Routines should be aware of this, so when Cache or Auth routines get implemented we could respond 401, 304 and similar status codes right from them.

Currently, if I'm not mistaken, Respect doesn't use any header() calls yet.

[alganet]

Also, we could support the OPTIONS method transparently (with the possibility to override it with a custom route) that responds with route information for specific routes or "*". I like a lot where this is going =D

[ramsey]

As well as the HEAD method, which would just return the exact headers returned on a GET request, without the response body.

[augustohp]

As seen in the commit above, it fixes this issue, but as in #25 we should implement some api to do header manipulation as seen on #28.