Missing POST route does not cause an error

[aalmiray]

Following Tim's recent Ratpack presentation at 33rd Degree

https://github.com/tlberglund/33rd-degree-ratpack

At one point the application had a GET route defined as

get('/lookup') {
    render('artist.html')
}

The template artists.html had a form with POST as the method. Clicking on the button produced an empty page. There was no error on the console. I believe this case should cause and error as there is no exact route defined for POST('/lookup') and apparently GET('/lookup') did not handle the request either.

[ldaley]

It does do the right thing from a HTTP point of view in that it returns a 405 response. What's missing though is the a way to have pretty HTTP response code pages.

Fancy contributing? :)