Error pages

Looking at a lot of VCL example, this seems to be a standard pattern.

Of all the other options, this wins on simplicity.

1. If a backend throws an error we catch it in vcl_fetch and pass it to vcl_error
2. vcl_error generates a synthetic page.
3. The page points at the heroku error app (via an iframe).

RE: earlier approach. Piping back errors in to the stack that generated the error seems fraught with danger. This makes a clean break. The error application is very decoupled from the rest of the stack.

/cc @wheresrhys