Yeah, regardless of what you put in the body, it would be nice to include a snippet of the error message in the place where HTTP says it should go...

On Apr 25, 2013, at 8:30 AM, Daniel Capo Sobral <notifications@github.com> wrote:

> In core/src/main/scala/blueeyes/core/http/HttpResponse.scala:
> 
> > @@ -16,9 +17,9 @@ sealed case class HttpResponse[+T](
> >  object HttpResponse {
> >    def empty[T] = HttpResponse[T](content = None)
> >  
> > -  def apply[T](th: Throwable): HttpResponse[T] = th match {
> > -    case e: HttpException => HttpResponse[T](HttpStatus(e.failure, e.reason))
> > -    case e => HttpResponse[T](HttpStatus(HttpStatusCodes.InternalServerError, Option(e.getMessage).getOrElse("")))
> > +  def error[T](th: Throwable)(implicit decode: String => T): HttpResponse[T] = th match {
> > +    case e: HttpException => HttpResponse[T](HttpStatus(e.failure), headers = HttpHeaders(`Content-Type`(text/plain)), content = Some(decode(e.reason)))
> Couldn't we compromise and also provide a length-limited message as the status message? It would help debugging at the network level, though, I grant, not that much.
> 
> —
> Reply to this email directly or view it on GitHub.
>