Set X-Forwarded-Proto Header

Heroku passes the X-Forwarded-Proto header to indicate the protocol of
the incoming request[1]. Ruby's rack relies on this header to
determine if a request is HTTPS[2].

Also, the X-Scheme header was removed to eliminate redundant passing of
the scheme.

[1]: https://devcenter.heroku.com/articles/http-routing#heroku-headers
[2]: https://github.com/rack/rack/blob/master/lib/rack/request.rb#L77
Add X-Forwarded-Port and X-Request-Start

Adding additional proxy headers to match what Heroku provides. Also,
X-Request-Start is compatible with NewRelic's latest agent[1].

[1]: http://blog.newrelic.com/2013/02/21/using-new-relic-on-heroku-read-how-our-new-ruby-agent-measures-queue-time/
Merge pull request #204 from statianzo/forwarded-proto

Set X-Forwarded-Proto Header
Handle pipe failures
Use pre-built buildstep image from s3. Add option to build your own.
Merge pull request #215 from kanterov/master

Handle pipe failures