Struct actix_web::Scope

pub struct Scope<T = ScopeEndpoint, B = BoxBody> { /* fields omitted */ }

A collection of Routes, Resources, or other services that share a common path prefix.

The Scope’s path can contain dynamic segments. The dynamic segments can be extracted from requests using the Path extractor or with HttpRequest::match_info().

Avoid Trailing Slashes

Avoid using trailing slashes in the scope prefix (e.g., web::scope("/scope/")). It will almost certainly not have the expected behavior. See the documentation on resource definitions to understand why this is the case and how to correctly construct scope/prefix definitions.

Examples

use actix_web::{web, App, HttpResponse};

let app = App::new().service(
    web::scope("/{project_id}/")
        .service(web::resource("/path1").to(|| async { "OK" }))
        .service(web::resource("/path2").route(web::get().to(|| HttpResponse::Ok())))
        .service(web::resource("/path3").route(web::head().to(HttpResponse::MethodNotAllowed)))
);

In the above example three routes get registered:

• /{project_id}/path1 - responds to all HTTP methods
• /{project_id}/path2 - responds to GET requests
• /{project_id}/path3 - responds to HEAD requests

Implementations

impl Scope

pub fn new(path: &str) -> Scope

Create a new scope

impl<T, B> Scope<T, B> where
    T: ServiceFactory<ServiceRequest, Config = (), Response = ServiceResponse<B>, Error = Error, InitError = ()>,
    B: 'static, 

pub fn guard<G: Guard + 'static>(self, guard: G) -> Self

Add match guard to a scope.

use actix_web::{web, guard, App, HttpRequest, HttpResponse};

async fn index(data: web::Path<(String, String)>) -> &'static str {
    "Welcome!"
}

let app = App::new().service(
    web::scope("/app")
        .guard(guard::Header("content-type", "text/plain"))
        .route("/test1", web::get().to(index))
        .route("/test2", web::post().to(|r: HttpRequest| {
            HttpResponse::MethodNotAllowed()
        }))
);

pub fn app_data<U: 'static>(self, data: U) -> Self

Add scope data.

Data of different types from parent contexts will still be accessible. Any Data<T> types set here can be extracted in handlers using the Data<T> extractor.

Examples

use std::cell::Cell;
use actix_web::{web, App, HttpRequest, HttpResponse, Responder};

struct MyData {
    count: std::cell::Cell<usize>,
}

async fn handler(req: HttpRequest, counter: web::Data<MyData>) -> impl Responder {
    // note this cannot use the Data<T> extractor because it was not added with it
    let incr = *req.app_data::<usize>().unwrap();
    assert_eq!(incr, 3);

    // update counter using other value from app data
    counter.count.set(counter.count.get() + incr);

    HttpResponse::Ok().body(counter.count.get().to_string())
}

let app = App::new().service(
    web::scope("/app")
        .app_data(3usize)
        .app_data(web::Data::new(MyData { count: Default::default() }))
        .route("/", web::get().to(handler))
);

pub fn data<U: 'static>(self, data: U) -> Self

👎 Deprecated since 4.0.0:

Use .app_data(Data::new(val)) instead.

Add scope data after wrapping in Data<T>.

Deprecated in favor of app_data.

pub fn configure<F>(self, cfg_fn: F) -> Self where
    F: FnOnce(&mut ServiceConfig), 

Run external configuration as part of the scope building process.

This function is useful for moving parts of configuration to a different module or library. For example, some of the resource’s configuration could be moved to different module.

use actix_web::{web, middleware, App, HttpResponse};

// this function could be located in different module
fn config(cfg: &mut web::ServiceConfig) {
    cfg.service(web::resource("/test")
        .route(web::get().to(|| HttpResponse::Ok()))
        .route(web::head().to(|| HttpResponse::MethodNotAllowed()))
    );
}

let app = App::new()
    .wrap(middleware::Logger::default())
    .service(
        web::scope("/api")
            .configure(config)
    )
    .route("/index.html", web::get().to(|| HttpResponse::Ok()));

pub fn service<F>(self, factory: F) -> Self where
    F: HttpServiceFactory + 'static, 

Register HTTP service.

This is similar to App's service registration.

Actix Web provides several services implementations:

• Resource is an entry in resource table which corresponds to requested URL.
• Scope is a set of resources with common root path.
• “StaticFiles” is a service for static files support

use actix_web::{web, App, HttpRequest};

struct AppState;

async fn index(req: HttpRequest) -> &'static str {
    "Welcome!"
}

let app = App::new().service(
    web::scope("/app").service(
        web::scope("/v1")
            .service(web::resource("/test1").to(index)))
);

pub fn route(self, path: &str, route: Route) -> Self

Configure route for a specific path.

This is a simplified version of the Scope::service() method. This method can be called multiple times, in that case multiple resources with one route would be registered for same resource path.

use actix_web::{web, App, HttpResponse};

async fn index(data: web::Path<(String, String)>) -> &'static str {
    "Welcome!"
}

let app = App::new().service(
    web::scope("/app")
        .route("/test1", web::get().to(index))
        .route("/test2", web::post().to(|| HttpResponse::MethodNotAllowed()))
);

pub fn default_service<F, U>(self, f: F) -> Self where
    F: IntoServiceFactory<U, ServiceRequest>,
    U: ServiceFactory<ServiceRequest, Config = (), Response = ServiceResponse, Error = Error> + 'static,
    U::InitError: Debug, 

Default service to be used if no matching route could be found.

If default resource is not registered, app’s default resource is being used.

pub fn wrap<M, B1>(
    self,
    mw: M
) -> Scope<impl ServiceFactory<ServiceRequest, Config = (), Response = ServiceResponse<B1>, Error = Error, InitError = ()>, B1> where
    M: Transform<T::Service, ServiceRequest, Response = ServiceResponse<B1>, Error = Error, InitError = ()>, 

Registers middleware, in the form of a middleware component (type), that runs during inbound processing in the request life-cycle (request -> response), modifying request as necessary, across all requests managed by the Scope.

Use middleware when you need to read or modify every request in some way.

pub fn wrap_fn<F, R, B1>(
    self,
    mw: F
) -> Scope<impl ServiceFactory<ServiceRequest, Config = (), Response = ServiceResponse<B1>, Error = Error, InitError = ()>, B1> where
    F: Fn(ServiceRequest, &T::Service) -> R + Clone,
    R: Future<Output = Result<ServiceResponse<B1>, Error>>, 

Registers middleware, in the form of a closure, that runs during inbound processing in the request life-cycle (request -> response), modifying request as necessary, across all requests managed by the Scope.

Examples

use actix_service::Service;
use actix_web::{web, App};
use actix_web::http::header::{CONTENT_TYPE, HeaderValue};

async fn index() -> &'static str {
    "Welcome!"
}

let app = App::new().service(
    web::scope("/app")
        .wrap_fn(|req, srv| {
            let fut = srv.call(req);
            async {
                let mut res = fut.await?;
                res.headers_mut().insert(
                   CONTENT_TYPE, HeaderValue::from_static("text/plain"),
                );
                Ok(res)
            }
        })
        .route("/index.html", web::get().to(index)));

Trait Implementations

impl<T, B> HttpServiceFactory for Scope<T, B> where
    T: ServiceFactory<ServiceRequest, Config = (), Response = ServiceResponse<B>, Error = Error, InitError = ()> + 'static,
    B: MessageBody + 'static, 

fn register(self, config: &mut AppService)