Route matching will 404 if not matching the method, even if the endpoint exists

[Rican7]

Problem

If a route endpoint is matched, but the method used to get to the endpoint is not matched by a specified route, the router defaults to throwing a 404 error, which is not exactly what's happening.

Potential Resolution

Instead, too be more RESTful, we should let the developer/client know that the endpoint exists through a different method by sending back a 405 "Method Not Allowed" error.

Example

That way, when defining routes, we could simply do this:

<?php

respond( 'POST', '/user/profile/?', function( $request, $response, $app ) {
});

Without having to then do this for each route:

<?php

respond( '/user/profile/?', function( $request, $response, $app ) {
    if ( $request->method() != 'POST') {
        // Respond with 405
    }
});

As you can imagine, that would get pretty dirt over time with numerous routes or multiple methods per route.

[chriso]

I agree this is better than 404'ing. I haven't got time to refactor it at the moment but would gladly take a pull request

[Rican7]

Hmm. OK, I'll see what I can do.
The obvious challenge is adding the functionality while keeping the speed.

[Rican7]

Closing this issue, as you merged my changes from my Pull Request #56