Update layout.jade
prevent incorrect automatic OPTIONS responses

The router has automatic handling of OPTIONS based on the registered
routes, but if you make an OPTIONS request for an endpoint that does
not exist, then it will still return a 200 with nothing allowed.
Instead, we can let the request move on down the middleware chain. This
has two benefits: first, if the route was not defined and no other
middleware handles it, it will return with a 404. Secondly, if multiple
routers are used and a later one has the route or a custom OPTIONS
defined, the first router will not respond incorrectly.
3.4.8
backport dependency updates

- range parser 1.0.0
- fresh 0.2.1
- send 0.2.0
- cookie-signature 1.0.3
- merge-descriptors 0.0.2
bump deps
3.5.0
pin down less-middleware

Things are broken in 0.2 version of less-middleware so use 0.1 line
3.5.1
remove one feature description
Merge pull request #2047 from Pana/patch-1

remove one feature description
improve req.xhr test by verifying status code
Merge pull request #2053 from shawnzhu/fix-xhr-test

improve req.xhr test by verifying status code
make old middleware properties configurable

closes #2054
Readme: add Roman as lead maintainer

so people start emailing him instead of TJ :D
support non-ascii filenames in content-disposition headers
Express 4 now uses "method-override" external library.
Fixing bug when updating pet name in MVC example.
Merge pull request #2058 from thetalecrafter/content-disposition

support non-ascii filenames in content-disposition headers
trim_prefix causing --use-strict flag to fail

as specified in bug #2064 the `trim_prefix` function declaration within the `try/catch` causes problems when starting express with `--use_strict` directive.
Merge pull request #2065 from WebReflection/patch-1

trim_prefix causing --use-strict flag to fail