docs(API): fix the mess-up in the nested middleware
fix(Request): Improve HTTP_RANGE support

 - Add a test to check whether "bytes=" is supported
 - add a simple way to support the "bytes=" prefix by stripping it if present
This should not break backward compatibility.

Fix #380
Merge pull request #379 from jeffrey4l/wrong_doc

Fix the wrong doc in the falcon.API
Merge pull request #382 from Joacchim/master

Improve HTTP_RANGE support, Fix #380
Removed redundant call to upper

This is a minor performance tweak, and only affects the testing suite.
fix(errors): bring 404 and 405 errors into RFC compliance

Per RFC 7231 6.5 states that 4xx errors should include a message to the user.
Corrects the 404 and 405 errors so that developers may provide all the same options
as available with other errors (f.e description, title, etc) in order to make them
RFC compliance while preserving the same default behavior.

No breaking changes. Default behavior is same as legacy behavior.
Closes JIRA Issue #331.
fix(API): routing logic should be done after request mw

Routing logic should be done after the execution of request middleware. The execution of request middleware
should be aware of routing logic. A logRequest middleware could not be executed if routing fails, or a mw
can not be executed if a routing fails.
Merge pull request #390 from BenjamenMeyer/bugfix_http_not_allow_description_usage_rebase

fix(errors): bring 404 and 405 errors into RFC compliance
Merge pull request #381 from ealogar/bug/routing_after_req_mw

bug(API): routing logic should be done after request mw
Merge pull request #388 from xiaclo/patch-2

fix(testing): Removed redundant call to upper
feat(errors): allow raising Request Entity Too Large error

This patch adds the ability to now raise Request Entity Too Large error
directly, instead of just setting the status code on the Response
object.