4.2 KiB
Errors
Actix uses Error
type
and ResponseError
trait
for handling handler's errors.
Any error that implements the ResponseError
trait can be returned as an error value.
Handler can return an Result object; actix by default provides
Responder
implementation for compatible result types. Here is the implementation
definition:
impl<T: Responder, E: Into<Error>> Responder for Result<T, E>
And any error that implements ResponseError
can be converted into an Error
object.
For example, if the handler function returns io::Error
, it would be converted
into an HttpInternalServerError
response. Implementation for io::Error
is provided
by default.
# extern crate actix_web;
# use actix_web::*;
use std::io;
fn index(req: HttpRequest) -> io::Result<fs::NamedFile> {
Ok(fs::NamedFile::open("static/index.html")?)
}
#
# fn main() {
# Application::new()
# .resource(r"/a/index.html", |r| r.f(index))
# .finish();
# }
Custom error response
To add support for custom errors, all we need to do is just implement the ResponseError
trait
for the custom error type. The ResponseError
trait has a default implementation
for the error_response()
method: it generates a 500 response.
# extern crate actix_web;
#[macro_use] extern crate failure;
use actix_web::*;
#[derive(Fail, Debug)]
#[fail(display="my error")]
struct MyError {
name: &'static str
}
/// Use default implementation for `error_response()` method
impl error::ResponseError for MyError {}
fn index(req: HttpRequest) -> Result<&'static str, MyError> {
Err(MyError{name: "test"})
}
#
# fn main() {
# Application::new()
# .resource(r"/a/index.html", |r| r.f(index))
# .finish();
# }
In this example the index handler always returns a 500 response. But it is easy to return different responses for different types of errors.
# extern crate actix_web;
#[macro_use] extern crate failure;
use actix_web::*;
#[derive(Fail, Debug)]
enum MyError {
#[fail(display="internal error")]
InternalError,
#[fail(display="bad request")]
BadClientData,
#[fail(display="timeout")]
Timeout,
}
impl error::ResponseError for MyError {
fn error_response(&self) -> HttpResponse {
match *self {
MyError::InternalError => HttpResponse::new(
StatusCode::INTERNAL_SERVER_ERROR, Body::Empty),
MyError::BadClientData => HttpResponse::new(
StatusCode::BAD_REQUEST, Body::Empty),
MyError::Timeout => HttpResponse::new(
StatusCode::GATEWAY_TIMEOUT, Body::Empty),
}
}
}
fn index(req: HttpRequest) -> Result<&'static str, MyError> {
Err(MyError::BadClientData)
}
#
# fn main() {
# Application::new()
# .resource(r"/a/index.html", |r| r.f(index))
# .finish();
# }
Error helpers
Actix provides a set of error helper types. It is possible to use them for generating specific error responses. We can use helper types for the first example with custom error.
# extern crate actix_web;
#[macro_use] extern crate failure;
use actix_web::*;
#[derive(Debug)]
struct MyError {
name: &'static str
}
fn index(req: HttpRequest) -> Result<&'static str> {
let result: Result<&'static str, MyError> = Err(MyError{name: "test"});
Ok(result.map_err(|e| error::ErrorBadRequest(e))?)
}
# fn main() {
# Application::new()
# .resource(r"/a/index.html", |r| r.f(index))
# .finish();
# }
In this example, a BAD REQUEST response is generated for the MyError
error.
Error logging
Actix logs all errors with the log level WARN
. If log level set to DEBUG
and RUST_BACKTRACE
is enabled, the backtrace gets logged. The Error type uses
the cause's error backtrace if available. If the underlying failure does not provide
a backtrace, a new backtrace is constructed pointing to that conversion point
(rather than the origin of the error). This construction only happens if there
is no underlying backtrace; if it does have a backtrace, no new backtrace is constructed.
You can enable backtrace and debug logging with following command:
>> RUST_BACKTRACE=1 RUST_LOG=actix_web=debug cargo run