Using the Clogger middleware (http://rubydoc.info/gems/clogger/1.2.0/frames ) it's easy to monitor HTTP traffic to the static file server. This basic proposal results into logged data as:
$ catapult server
>> Thin web server (v1.5.1 codename Straight Razor)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:9292, CTRL+C to stop
"GET /movies.json HTTP/1.1" ? 404 0.000 0.0.0.0:9292
"GET /favicon.ico HTTP/1.1" ? 404 0.000 0.0.0.0:9292
I think this is especially helpful to see traces of 404's during development, and possibly 20x when connecting to APIs.
Using the Clogger middleware (http://rubydoc.info/gems/clogger/1.2.0/frames ) it's easy to monitor HTTP traffic to the static file server. This basic proposal results into logged data as:
I think this is especially helpful to see traces of 404's during development, and possibly 20x when connecting to APIs.